Package: debootstrap Version: 1.0.123 Severity: normal X-Debbugs-Cc: b...@debian.org
Hi - I'm using debootstrap to create a fresh new chroot, and it fails immediately: root:~# /usr/sbin/debootstrap --variant=buildd buster /var/chroot/buster-amd64 E: Unable to execute target architecture root:~# cat /var/chroot/buster-amd64/debootstrap/debootstrap.log amd64: not supported on this machine/kernel root:~# In this example, the directory /var/chroot/buster-amd64 did not previously exist. The problem appears to be at the arch-test stage (line 637 of /usr/sbin/debootstreap), where it runs 'arch-test -c "$TARGET" "$ARCH"' to see if the host and target architectures are compatible. AFAICT, when given a chroot via -c, arch-test looks for its test files *inside* the chroot; however, at this stage debootstrap has not yet done any unpacking (or even any downloads), which means the chroot is empty. This maks arch-test fail, even though the host and target architecture are identical, and in turn this makes debootstrap fail before it has a chance to do any real work. If I comment out the arch-test stage at line 632 (i.e., skipping the arch-test block entirely) then debootstrap runs successfully to completion. Thanks - Ben. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debootstrap depends on: ii wget 1.21-1+b1 Versions of packages debootstrap recommends: ii arch-test 0.17-1 ii debian-archive-keyring 2019.1 ii gnupg 2.2.27-1 Versions of packages debootstrap suggests: pn squid-deb-proxy-client <none> pn ubuntu-archive-keyring <none> -- no debconf information
