On Mon, 30 Dec 2024 at 20:30, Helmut Grohne <hel...@subdivi.de> wrote: > > Dear release team, > > On Sun, Dec 29, 2024 at 07:29:06PM +0000, Luca Boccassi wrote: > > We would like to remove the legacy usr-is-merged/usrmerge packages from > > testing/unstable, but debootstrap in bookworm still pulls usr-is-merged > > in manually and fails if it cannot be found. As you know, it is no > > longer necessary in testing/unstable as the work is done in base-files. > > > > I have uploaded debootstrap/1.0.128+nmu2+deb12u2 to bookworm-p-u with > > this change backported from unstable. debdiff attached. > > Please allow me to second the request. At this time, I am not sure > whether we will manage to remove usrmerge in the trixie cycle. Even if > we are not, it would be very useful if bookworm's debootstrap were to be > able to bootstrap forky and this is change is required there. > > I see a small risk of the change in matching having unintended effects > on derivatives that disguise themselves as Debian and have not yet > picked up the merge via base-files.
I don't think we should guide what we do for our stable point releases based on hypothetical derivatives. If you import our sources, you need to be on point with what we do, this is not news. The p-u freeze for the next point release is next weekend, and I would strongly prefer not to miss the boat, as the next one might clash with Trixie (we don't know yet). > Not sure we notice as the failure path should be installing > usrmerge via init-system-helpers. init-system-helpers no longer depends on usrmerge
