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
MSYS2 on Windows 10 - cannot update the package database using pacman #2589
Comments
There is something wrong in your pc setup. Antivirus software may delete files without any reason. To workaround this situation
|
I only have the Windows 10 antivirus that comes with the OS. I do not have any other antivirus software. I downloaded the file then opened MSYS2 and ran the command. I get the same error:
It seems to me that I can't run any pacman command. You say to run that command but where do I run it, in MSYS2? If I run it with MSYS2, do I move the downloaded file to a specific directory or will the downloaded file just be detected automatically anywhere on my system? It's in my download folder right now. Thank you. |
Create that empty file as you have said in original post. Then run the
Any msys2/mingw window.
You need to specify the full path of that .pkg.tar.zst file in that |
Another user had the same problem: https://stackoverflow.com/q/68562503 |
Thank you that seems to have worked (sort of). Now I only get this error:
I think I have to add to the repository or something like that but I am not too sure. Thank you again for helping. |
|
Thank you so much, it works perfectly now. |
I tried to update my MSYS2 on Windows 10 (as per the instructions on https://www.msys2.org/) and I got this error:
So I did a fresh install of MSYS2 on Windows 10. I got the binaries from the MSYS2 website and installed it successfully. Now, I am getting the same error.
I went into the /etc/pacman.d/ directory and this is what was inside:
I didn't find the file so I created an empty file with the name "mirrorlist.mingw" and ran the update but to no avail. So I just deleted the empty file I created. No other flags like -S, -Su, or -Syy, etc. work and produce the same error.
Thank you.
The text was updated successfully, but these errors were encountered: