Implementing /Usr Merge in Alpine
alpinelinux.org
Implementing /Usr Merge in Alpine
1–10 of 32 posts
Re: Implementing /Usr Merge in Alpine
#2>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.
Re: Implementing /Usr Merge in Alpine
#3I feel like they jumped the gun on this article. 3.22 does not have a merge-usr package/script in http://dl-cdn.alpinelinux.org/alpine/v3.22/main and 3.23 does not yet exist otherwise I would test the merge script right now on a throw-away VM. Looking at the merge request it appears the Finish step is not yet completed or the pipeline was skipped or I am reading this incorrectly. Perhaps they are just missing an estimated deployment date in the article.
Re: Implementing /Usr Merge in Alpine
#4I feel like they jumped the gun on this article. 3.22 does not have a merge-usr package/script in http://dl-cdn.alpinelinux.org/alpine/v3.22/main and 3.23 does not yet exist otherwise I would test the merge script right now on a throw-away VM. Looking at the merge request it appears the Finish step is not yet completed or the pipeline was skipped or I am reading this incorrectly. Perhaps they are just missing an esti…
As TFA says, currently the usr-merge and the script for it is only in Edge, and it will come to stable in 3.23
Re: Implementing /Usr Merge in Alpine
#5>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.
Re: Implementing /Usr Merge in Alpine
#6>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 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.
Re: Implementing /Usr Merge in Alpine
#7I feel like they jumped the gun on this article. 3.22 does not have a merge-usr package/script in http://dl-cdn.alpinelinux.org/alpine/v3.22/main and 3.23 does not yet exist otherwise I would test the merge script right now on a throw-away VM. Looking at the merge request it appears the Finish step is not yet completed or the pipeline was skipped or I am reading this incorrectly. Perhaps they are just missing an esti…
As TFA says, currently the usr-merge and the script for it is only in Edge, and it will come to stable in 3.23
I've read the article 5 times and I can almost interpret it that way in the how to migrate section which mentions 3.23. The Timeline section has no mention of dates. I would like to see a table of dates or at least an Oompa Loompa song.
Re: Implementing /Usr Merge in Alpine
#8>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 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.
Re: Implementing /Usr Merge in Alpine
#9Earlier quoted context omitted.
As TFA says, currently the usr-merge and the script for it is only in Edge, and it will come to stable in 3.23
I've read the article 5 times and I can almost interpret it that way in the how to migrate section which mentions 3.23. The Timeline section has no mention of dates. I would like to see a table of dates or at least an Oompa Loompa song.
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.
Re: Implementing /Usr Merge in Alpine
#10Earlier quoted context omitted.
I've read the article 5 times and I can almost interpret it that way in the how to migrate section which mentions 3.23. The Timeline section has no mention of dates. I would like to see a table of dates or at least an Oompa Loompa song.
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.