11–20 of 32 posts
>and non-merged installations upgrading to it will break. This is unacceptable. Updating your operating system should not cause it to break. Alpine should be responsible for the migration and not forcing users to do manual work else breaking their machines.
>and non-merged installations upgrading to it will break. This is unacceptable. Updating your operating system should not cause it to break. Alpine should be responsible for the migration and not forcing users to do manual work else breaking their machines.
The only way it can break is if you skip straight to forward to a release that no longer contains the tooling allowing you to make the transition cleanly. They outlined this is the article.
Earlier quoted context omitted.
There's no need to interpret anything. It's spelled out in the list in the Timeline section already. Point 1 tells you it's in Edge. Point 2 tells you that stable will be able to start migrating with 3.23, ie when current Edge becomes stable.
I am not seeing the same thing as you. The timeline section says that if I install 3.23 it will be user-merged and if I upgrade from an older release I wont be forced until 3.26. There are no dates. A timeline will have times and/or dates. Perhaps it is a CDN caching issue.
>>Release of Alpine Linux __3.23: [...] From this point onwards,__ users are encouraged to migrate existing installs.
Earlier quoted context omitted.
I am not seeing the same thing as you. The timeline section says that if I install 3.23 it will be user-merged and if I upgrade from an older release I wont be forced until 3.26. There are no dates. A timeline will have times and/or dates. Perhaps it is a CDN caching issue.
>>the Merge Request that finalizes the initial work will be merged. Any new __edge__ installations will be /usr-merged from this point onwards. >>Release of Alpine Linux __3.23: [...] From this point onwards,__ users are encouraged to migrate existing installs.
Earlier quoted context omitted.
>>the Merge Request that finalizes the initial work will be merged. Any new __edge__ installations will be /usr-merged from this point onwards. >>Release of Alpine Linux __3.23: [...] From this point onwards,__ users are encouraged to migrate existing installs.
Not OP, but I think OP is looking for dates, as in a year, month, day, situation—not only version numbers. I think they want to know what specific date 3.23 will be released with this change.
Earlier quoted context omitted.
Not OP, but I think OP is looking for dates, as in a year, month, day, situation—not only version numbers. I think they want to know what specific date 3.23 will be released with this change.
They didn't understand the version numbers (notice they were complaining that the blog post jumped the gun because there is no merge-usr in 3.22) and wanted dates. I explained the version numbers to them. Yes, there are no dates; Alpine never gives expected dates for future releases because nobody knows what they are.
To OP: this announcement from Alpine doesn't contain dates, like you've mentioned. This is apparently not an accident.
Earlier quoted context omitted.
Not OP, but I think OP is looking for dates, as in a year, month, day, situation—not only version numbers. I think they want to know what specific date 3.23 will be released with this change.
They didn't understand the version numbers (notice they were complaining that the blog post jumped the gun because there is no merge-usr in 3.22) and wanted dates. I explained the version numbers to them. Yes, there are no dates; Alpine never gives expected dates for future releases because nobody knows what they are.
>and non-merged installations upgrading to it will break. This is unacceptable. Updating your operating system should not cause it to break. Alpine should be responsible for the migration and not forcing users to do manual work else breaking their machines.
This or at very least wait until a major version update like 4.0 so that if an installation breaks it's likely during a major uplift or refresh or greenfield deployment.
Earlier quoted context omitted.
Alpine isn't a distro one would upgrade. It is usually used for throwaway containers, so the upgrade path is clear: throw the old one away, create a new one.
I have Alpine installed on many physical and virtual machines all around the USA. I know I am not alone on this. Some VPS providers also offer it as an installation option and some VM's are long-lived.
I run Alpine on metal, and I approve TFA. Thank you to the alpine team for your transparency and your efforts!
>and non-merged installations upgrading to it will break. This is unacceptable. Updating your operating system should not cause it to break. Alpine should be responsible for the migration and not forcing users to do manual work else breaking their machines.
> Alpine should be responsible
"AS IS" WITHOUT WARRANTY OF ANY KIND