Dear Maintainer,

Since --merged-usr is default in this configuration, it doesn't have to
be passed.

ARCH can be amd64 or arm64

debootstrap --variant=minbase --arch=$ARCH --components main,contrib,non-free,non-free-firmware bookworm /lava-files/rootfs-amd64/ http://deb.debian.org/debian

leads to errors as:
...
W: Failure while unpacking required packages.  This will be attempted up to five times.
W: See /lava-files/rootfs-amd64/debootstrap/debootstrap.log for details (possibly the package /var/cache/apt/archives/usr-is-merged_35_all.deb is at fault)

Whole log: https://gitlab.freedesktop.org/okias/mesa/-/jobs/38725690

These errors can be prevented when using --no-merged-usr.

I'm having this problem in bookworm, even with --no-merged-usr:

$ debootstrap --no-merged-usr sid /var/tmp/chroot/
[...]
I: Unpacking tzdata...
I: Unpacking usr-is-merged...
I: Unpacking zlib1g:amd64...
W: Failure while unpacking required packages.  This will be attempted up to five times.
W: See /var/tmp/chroot/debootstrap/debootstrap.log for details (possibly the package /var/cache/apt/archives/usr-is-merged_38_all.deb is at fault)

Because of this I cannot use pbuilder.

Berto

This works fine if I install the package from bookworm-backports
(1.0.133~bpo12+1) so the package in stable should be fixed

Berto

Hi, I have tripped onto this while following blindly the automatic
sbuild setup using sbuild-debian-developer-setup described here:
https://wiki.debian.org/sbuild#Automatic_setup_using_sbuild-debian-developer-setup

Alberto's workaround (sudo apt install -t bookworm-backports
debootstrap) worked for me.

Paolo

Control: fixed -1 1.0.128+nmu2+deb12u1

This is working fine with the new version of debootstrap in bookworm,
i.e version 1.0.128+nmu2+deb12u1 from Debian 12.4

Berto

This fails on a number of host/target combinations, but not all of them.

A mips64el target, for example, fails every time.

Would the maintainer(s) prefer separate bugs for each arch? The fault(s)
may not lie in the debootstrap package.

debootstrap 1.0.134