-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Remove msys2 hacks and vendor the whole thing #65767
Comments
msys2 is using See here for more descriptions about it. |
@crlf0710 that would be nice but msys doesn't remove old packages from their repo so the mirror would be enormous. Also extracting it from archive would make CI a bit faster because you won't be modifying thousands of small files over and over. On Linux that is not a problem but |
…mulacrum [beta] ci: revert msys2 ca-certificates hack The hack was added because upstream msys2 broke the ca-certificates package, but since then it has been fixed. This reverts CI to use the upstream package. Part of #65767 r? @Mark-Simulacrum
…ck, r=Mark-Simulacrum ci: revert msys2 ca-certificates hack The hack was added because upstream msys2 broke the ca-certificates package, but since then it has been fixed. This reverts CI to use the upstream package. Part of rust-lang#65767
No update on this, planning to discuss what to vendor at the all hands. |
At the last infra meeting we decided a good step is to move towards using the pre-installed msys2 packages. In theory this is as simple as removing the msys2 installation step and pointing things at the right location on the images in CI. |
On 2019-10-24 we had a CI outage due to the ca-certificates msys2 package being broken. The hack @mati865 implemented (:heart:) is to download an older, known good package beforehand and install it after msys2 updated its packages.
Once msys2/MINGW-packages#5887 is fixed we should revert the hack, but I think at this point it's worth investing in vendoring msys2 as a whole.
The text was updated successfully, but these errors were encountered: