Install target mingw packages, no partial upgrade #38
Conversation
|
Thanks. Let me look into this... |
|
I probably messed something up when packaging in |
No, that isn't the issue. This is something that happened once before. Can you check this now? If a repo has no commits, GitHub Actions cron jobs stop running after some time interval that cannot be changed. The MSYS2 archive files are created by https://github.com/ruby/setup-msys2-gcc, and the CI there stopped. I just reenabled them, and ran the CI. I'm going to set more frequent reminders to check that, or maybe make a commit once every two weeks... |
What do I need to do? Force-push? |
|
Sorry, nothing to do here. I'm checking whether this is fixed. CI Is running right now, added clang to a Puma run in my fork. It also uses this repo's action. CI passed (installed clang), so your RubyGems workflows should be passing now. Also, no need for this PR. |
|
See https://github.com/MSP-Greg/puma/actions/runs/7758399762/job/21160121413#step:5:81 That job installed clang... |
|
Things were broken for us an hour ago, that's why I started troubleshooting this. Glad it's all good now. |
|
It does seem better to me regardless to not upgrade anything under the hood unless not explicitly requested, even more knowing that this has indeed broken at some point and that https://github.com/msys2/MINGW-packages/ maintainers stated But this is totally up to you! |
A package change in msys2/MINGW-packages#19913 made this pacman command to start failing.
See for example https://github.com/rubygems/rubygems/actions/runs/7755580051/job/21151329683?pr=7422.
Upstream they recommended to run either
-S(no upgrade) or-Syu(full upgrade).I went with the former because it seems like a more deterministic thing to do.