-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WinXP] Doesn't work when installed on drive D:\ #603
Comments
My MSYS2, which I installed some time last year, is installed in |
I use 32-bit version on Windows XP, perhaps this matters. |
Win 10 here, MSYS2 installed |
Make sure that drive's file system is NTFS. A lot of packages use hard links which don't work with FAT32/exFAT drives. |
Of course it's NTFS, it's just a non-system partition of the same drive, nothing non-standard. Thanks for the try though. |
|
Thanks for the feedback. So it looks like the problem is with Windows XP, I'll update the title. Meanwhile I tried to update everything on C: and then move msys32 to D:, but to no avail. |
You could try to change permissions (maybe there is read only mark) for msys directory. If this doesn't help temporary turn off antivirus. |
there is an |
I've unchecked indeterminate-state "Read only" on "msys32" and applied it all to files and subdirectories, it led to no changes with pacman, and it's indeterminate again when I open Properties next time. But I suppose there's no problem with permissions: first, it works Ok when moved to C:, second, actually all other files except running executables are updating successfully. Re-installation of core packages by that procedure says that everything is up to date. And I have nothing else to do there, since I don't have any custom packages installed (pacman doesn't work), it's a fresh new install. I believe I opened an issue in a wrong repository, perhaps it should've been msys2-pacman. |
Thank you labeling. |
Latest versions do not work on WinXP anymore anyway. |
The symptoms are just like in #567, on
pacman -Sy pacman
it silently fails with these messages:And despite them the package is considered installed after this, when in fact the binary is the old one.
The same kind of problem appear when trying to update anything else.
The text was updated successfully, but these errors were encountered: