> > Just create the chroot for the CI with --merged-usr and all will be
> > fine. Debootstrap in Buster is not going to be updated to do it
> > automatically, only in Bookworm/Bullseye.
> Thanks Luca for clarification. So seems we need to get bookworm
> removed from 
> https://github.com/debuerreotype/debuerreotype/blob/60b625d1ce31bd81525bb67fc3a33f9686bc3433/examples/debian.sh#L183
> so that the 'debuerreotype' will run debootstrap for both bookworm and
> bullseye with '--usr-merged'. Once that is done, we need to wait for
> to the code in 
> https://github.com/debuerreotype/docker-debian-artifacts/tree/dist-amd64
> to run to generate new images of official Debian Docker images at
> https://hub.docker.com/_/debian.
> This will fix upgrade testing from Bullseye to Bookworm if I
> understood correctly.

Turns out the usrmerge changes are has a bit of complexity in
debuerrotype (e.g.
but based on comments in
and https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/76
at least you Luca are already aware of them.

Seems that doing a drive-by-contribution to debyerrotype is too much
of a learning curve for me, so I will embark on finding other
workarounds to get CI systems working again past the
Buster-Bullseye-Bookworm upgrade.

Reply via email to