Hi! On Wed, 2023-03-08 at 14:26:13 +0100, Guilhem Moulin wrote: > On Wed, 08 Mar 2023 at 14:11:05 +0100, Christoph Anton Mitterer wrote: > > On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote: > >> No please don't, #-1 is RC so that would block transitioning into > >> Bookworm which only supports merged-usr… Will fix that later during > >> the > >> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not > >> further delay the transition. > > > > Well but at least right now people without merged /usr will still end > > up in a broken system? > > Yes. Been the case for a week (since the argon2=0~20190702-0.1 upload). > However the TC has ruled that these systems are no longer supported, so > the issue isn't RC. Not saying we should shove it under the carpet, > only that it shouldn't delay transition.
That's not what the TC ruled though, see: https://lists.debian.org/debian-devel/2021/10/msg00190.html Where this is covered explicitly: ,--- - Because Debian 11 installations with the non-merged-/usr layout already exist, all packages in Debian 12 should be installable onto a non-merged-/usr system along with their dependencies, and work correctly on the resulting system. + The key reason for this is that apt is not required to perform the upgrade between stable releases in any particular order, so long as package dependency relationships are respected; therefore the upgrade can happen in whatever order apt chooses, which can vary between machines. Debian has not traditionally required use of a special upgrade tool similar to Ubuntu's do-release-upgrade(8) and we believe the upgrade to Debian 12 should be no different (see below for more details on this topic). + Another reason for this is that during the development of Debian 12, testing/unstable systems undergo a series of partial upgrades, which similarly will happen in an undefined order. + We do not require that the resulting system remains non-merged-/usr: if the packages involved in this installation transaction are part of the implementation of a transition to merged-/usr, then installing them might result in the system becoming merged-/usr. - The same expectations apply to packages uploaded to testing/unstable during the development cycle that will lead to Debian 12. `--- > > And there is no guarantee that /usr has already been merged at that > > point... I mean it should, when the upgrade to bookwork completes... > > but can it happen that it's interrupted? Or that people do it in > > several steps? Then they could upgrade argon2, reboot and have the > > missing libgcc. > > Correct, but AFAICT that's would be a FrankenDebian so not something > supported either. Either way that's not something src:cryptsetup can > fix. One could upload src:argon2 again adding “Break: cryptsetup-initramfs > (<< 2:2.6.1-2)” to libargon2-1, though I'm not sure it's worth doing > given the freeze and the fact that covered that supported systems are > covered. Partial upgrades is the expected state you get when upgrading from Debian N to Debian N+1. Thanks, Guillem