Hi Santiago, Quoting Santiago Vila (2024-08-29 14:02:43) > Lee Garret wrote: > > when creating a bookworm schroot e.g. with > > sbuild-createchroot --merged-usr bookworm > > /var/lib/schroot/schroots/bookworm-amd64-sbuild > > http://localhost:3142/deb.debian.org/debian/ > > the resulting schroot has an unmerged /usr. > > I'm doing this: > > sbuild-createchroot --merged-usr bookworm /tmp/mychroot > http://deb.debian.org/debian > > and it works for me. I get a usrmerged system that way. > > I'm using sbuild and debootstrap in bookworm > (i.e. 0.85.0 and 1.0.128+nmu2+deb12u1).
I can confirm this on bookworm. > Johannes Schauer Marin Rodrigues wrote: > > Do you think that this change addresses your concerns? > > I don't. If it works in bookworm, I don't see a good reason > why it should suddenly stop working. > > In fact, without --merged-usr, a non usrmerged is created > but having the usr-is-merged package installed. That's very bad and I hope > somebody can address it. So now there are multiple bugs. One is, that on bookworm, --merged-usr --variant=buildd is creating a merged-/usr chroot. The other bug is that in unstable, there is nothing in the debootstrap output which tells the user that their bookworm buildd chroot will not be merged despite that flag. We have to talk to more people to figure out how this is supposed to work... Thanks! cheers, josch
signature.asc
Description: signature
