Package: arch-test Version: 0.22-1 Severity: normal X-Debbugs-Cc: [email protected]
Hi, arch-test currently respects the $CHROOT environment variable. If the user has it set, then it will be as if --chroot was passed to arch-test. Maybe this is intentional so that arch-test can be called with a chroot even in situations where one does not have direct control over the arch-test call? Michael Tokarev (CC) found this bug when running mmdebstrap with CHROOT=unstable-amd64 set which is done by the rust development tools. This will make arch-test and thus mmdebstrap fail if unstable-amd64 does not contain the expected contents. The CHROOT variable is not set up for the use of arch-test so mmdebstrap will fail in this case. I could remove the CHROOT variable from the environment before calling arch-test from mmdebstrap but before doing that I wanted to give you a heads-up about this behaviour and allow you to either: * confirm that this is intentional (and then maybe mention this in the man page of arch-test) or * add a CHROOT= in front of the option parsing loop so that whatever the environment contains is ignored Thanks! cheers, josch -- System Information: Debian Release: 13.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: arm64 (aarch64) Foreign Architectures: armhf, i386, amd64 Kernel: Linux 6.12.43+1-mnt-reform-arm64 (SMP w/6 CPU threads) Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- debconf-show failed
