Switch from usrmerge to usr-is-merged
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Confirmed
|
Undecided
|
Unassigned | ||
init-system-helpers (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Last year in Debian we added the 'usr-is-merged' binary package to the 'usrmerge' source package. Its purpose is to be an empty metapackage that simply asserts that the system is usr-merged. This is done via the postinst. Contrary to usrmerge, it doesn't ship any additional code, perform any additional action or have any additional dependencies.
In Debian, we have an essential package (init-system-
But for new images being built, the boostrap (eg: debootstrap) process will instead pull in usr-is-merged, which will save space and reduce the overall code footprint.
The problem in Ubuntu is that while usrmerge is in main, usr-is-merged is in universe, so unless the bootstrap tool enables universe for the initial bootstrap phase, usrmerge is always pulled in.
Refs:
https:/
https:/
https:/
Related branches
- Steve Langasek: Disapprove
- Matthieuj Clemenceau: Pending requested
- Éric St-Jean: Pending (forward to engineer of your choice) requested
-
Diff: 11 lines (+3/-0)1 file modifiedsupported-installer-common (+3/-0)
tags: | added: cpc-2836 |
Thanks Luca,
I think it is no problem at all to promote usr-is-merged to main.
And while this would only save a few bytes on a new image we have to be clear that any win is a win.
Especially since so many other changes keep increasing image size.
Currently seeded into the ISO builds:
usrmerge (from usrmerge) is seeded in:
edubuntu: daily-live
kubuntu: daily-live
lubuntu: daily-live
ubuntu-base: daily
ubuntu-budgie: daily-legacy, daily-live
ubuntu-mate: daily-live
ubuntu-server: daily-live, daily-preinstalled
ubuntu-unity: daily-live
ubuntu: daily-canary, daily-legacy, daily-live, daily-preinstalled
ubuntucinnamon: daily-live
ubuntukylin: daily-live
ubuntustudio: dvd
xubuntu: daily-live, daily-minimal
IMHO We'd actually want to keep both in main in any case and should do so to stay there independent to their seeding in an iso/image to avoid noise of moving in/out based on changes to their build.