On Thu, 29 Aug 2024 at 14:02:43 +0200, Santiago Vila wrote:
> In fact, without --merged-usr, a non usrmerged is created
> but having the usr-is-merged package installed.

When creating a Debian 12 chroot, this is non-obvious but is actually
working as designed. As part of the transition from "merged-/usr is
opt-in" to "merged-/usr is the default" in Debian 12, the usr-is-merged
package was repurposed from meaning "/usr is merged" (as it did in
Debian 11) to meaning: either /usr is merged, or the operator of the
chroot/container has explicitly opted-out of merged-/usr (which implies
also opting out from the ability to upgrade to trixie) by creating the
flag file /etc/unsupported-skip-usrmerge-conversion.

This opt-out was technically possible from usrmerge 27 to 37 inclusive. It
is no longer possible in trixie/sid, in which usr-is-merged (>= 38) and
base-files (>= 13.3) enforce a merged-/usr layout.

For Debian 12, the TC advised in resolution #994388 [1] that bugs of the
same category as #993675 [2] should be treated as RC, consistent with the
earlier resolution #914897 [3] (see ยง(Building packages) in #994388).

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#110
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993675
[3] https://lists.debian.org/debian-devel-announce/2019/03/msg00001.html

However, as a courtesy to users upgrading packages with that category of
bug from Debian 11, official buildds for Debian 12 and older use a
non-merged-/usr build chroot, because that is the layout that is most
likely to result in a .deb that works equally well on either merged-/usr
or non-merged-/usr systems during the upgrade from Debian 11 to 12.

    smcv

Reply via email to