-
Notifications
You must be signed in to change notification settings - Fork 488
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
Update to Cygwin 3.5 - The end for Windows 7/8 #4425
Comments
Someone suggested to use the pre_install/upgrade script to abort things. |
And as noted, having a 3.4 package should be viable: #4422 (comment) |
When installing msys2-runtime-3.3, I tend to use |
Yeah, it wont be as smooth as a normal update. We could do a "startswith msys2-runtime" or check its provides to treat it as a core update. edit: I've filed msys2/msys2-pacman#39 |
I see that
but on
still |
So we can test it. I've been using it locally for the last few weeks. This will change with #4580 |
With #4576 in the repo now Windows 7 users will see pacman abort and the message suggesting the move to msys2-runtime-3.4 (see screenshot above) Next steps:
|
All done now. |
@lazka When I updated today on Windows 10, the As you've already noticed, it works fine with pacman -Su
|
I had a |
I've reverted the update script change today to rule out any problems re #4585 (and adjusted the NEWS entry on the website accordingly). The "failed" thing you saw is I think just because the script is also called after the update, so in theory it failing there shouldn't matter. But I reverted it to be save. I'd rather have working upgrades then make things easier for win 7 users. Hooks are ignored for core upgrades: msys2/msys2-pacman@9d91ab9#diff-5add07940112341f59fe3817d1d534ef87c348c83ea1109660789d444e93da5aR810 |
Thanks for the info! I maybe found an easy way to fix the annoying errors.
The thing that puzzled me was, why is pre_upgrade() running after the runtime package is installed, instead of before? After a bit of looking, the answer is too simple: it's running twice, each time as expected before a package is installed, once each for msys2-runtime and msys2-runtime-devel. So I rolled my installation back and re-updated with a locally built 3.5.3-1, adding a pacman -Su # (Windows 10)
Maybe I'm missing something and this is all wrong, so I'll let you decide if you want to implement it. |
After looking at the code base I can see it would be challenging to selectively disable post- hooks for core. But a pre- hook with This may not be as bad as I'm thinking; what I don't know is:
Just thinking out loud. |
I am confused about which one is newer. 3.4.10-3 3.4.10-10 |
Are there mirrors that store old packages? I'm looking to archive the latest versions of packages compatible with msys2-runtime 3.4 and set up a mirror for Windows 7 users. |
It is pretty clear. But note the different package names: |
Once we update to cygwin 3.5, users still on Windows 7/8 who upgrade will break their installation.
The PR for this would be #4422
Currently ~0.5% of users are affected, but it's not clear how many of them update things. #2832 (comment)
I guess the next thing is to write a NEWS entry for them, tell them how to fix their install if it's broken, and that they can't update anymore.
The text was updated successfully, but these errors were encountered: