Hi Helmut, Thanks for the background and proposed course of action.
Helmut Grohne <hel...@subdivi.de> (2024-12-29): > The obvious part is that we no longer technically need > usr-is-merged to get installed. debootstrap should stop doing it. > I am attaching a patch to that effect. Unfortunately, we also want > to use bookworm's debootstrap to bootstrap trixie and that's not > as easy. So at least for the time being, reintroducing usrmerge > will be needed. Cyril indicated that he did a reintroducing NMU on > #1088212, so I assume that this is being taken care of and needs > no further action. Yes, that's in progress. That's really a band-aid to avoid respinning too many things on the d-i side, for this release specifically. I can totally understand why folks want to get rid of a package that was only meant to be transient. > Recommended course of action: > 1. Revert the removal. (done by Cyril afaiui) > 2. Apply the attached patch. > 3. SPU the attached patch. > 4. Wait for a stable point release. > 5. Retry usrmerge removal (before the transition freeze or in forky). That puts a requirement on users to catch up with the point release if they want to keep being able to debootstrap trixie/sid once the removal happens (again), which can be surprising / a little point of friction, but that's much better than previous situations (where debootstrap broke and the fix was only available in proposed-updates). Indeed in that case, the support side that's much easier (“just dist-upgrade your stable system”) than what happened a while back (“add proposed-updates, install stuff from there, maybe get other package updates, etc.”). Out of curiosity (and I'm not advocating for or requesting that): how much of a hassle would it be to just ship the package in trixie? > Hope this all makes sense and sorry for the inconvenience caused to > d-i. Except for the little digression above, I'll stay focused on trying to get Trixie Alpha 1 out (I'd like to stick to at most a few days of partial freeze each time, to minimize the impact on other developers, esp. with the real freeze getting closer), and let others comment on the stable vs. testing/unstable aspects. (I'll probably get looped in anyway, when the proposed-updates request reaches the release team…) Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
