On Thu, 29 Aug 2024 at 14:14:00 +0200, Santiago Vila wrote: > Chris Hofstaedtler wrote: > > And yes, upgrading [unmerged-/usr bookworm chroots] is not supported. > > I don't see any good reason why a chroot created by a (non-buggy version of) > sbuild or debootstrap could not be upgraded.
Upgrading a non-merged-/usr bookworm chroot with bookworm security/stable updates is OK, you can do that. Upgrading a non-merged-/usr bookworm chroot to trixie/sid is explicitly not supported. This transition had 4 stages: 1. Only non-merged-/usr is supported (approximately Debian <= 9) 2. Both merged-/usr and non-merged-/usr are supported (Debian 10 and 11) 3. In general all installations should be merged-/usr, but disposable chroots/containers used for buildds and QA can still be forced to be non-merged-/usr, and upgrades from Debian 11 also need to work, so every package must still be installable either way (Debian 12) 4. Everything must be merged-/usr and packages are allowed to assume it (Debian 13) We have to draw a line somewhere for the break between (3.) and (4.), and as per TC resolution #994388 in 2021 [1], the place where that line was drawn is, in theory, trixie/sid immediately after the bookworm release. (In practice, it was unsupported but sort-of-worked until usrmerge (>= 38) and then base-files (>= 13.3) made merged-/usr genuinely unavoidable.) [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#110 > We need that to work to be able to test things. If you are doing upgrade tests from bookworm to trixie/sid (piuparts or similar), TC resolution #994388 says you can't validly use a non-merged-/usr chroot for that. Please use a separate merged-/usr base chroot or tarball for that. It's probably also better to use --variant=minbase rather than --variant=buildd for this sort of tests, which is another reason why sbuild-createchroot is not the most appropriate tool for purposes other than sbuild. smcv
