Control: fixed-upstream On Sat, Nov 15, 2025 at 06:22:51AM +0100, Johannes Schauer Marin Rodrigues wrote: > Package: arch-test > Version: 0.22-1 > Severity: normal
> 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? If I recall correctly, it's unintentional -- shell merely inherits variables from the environment. And it's unlikely that anyone relies on the variable rather than -c. Heck, the very -c option is obsolete now, it made sense when qemu-user had to live inside the chroot. > * add a CHROOT= in front of the option parsing loop so that whatever > the environment contains is ignored Done, in git. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ .globl _start↵.data↵rc: .ascii "/etc/init.d/rcS\0"↵.text↵_start ⣾⠁⢠⠒⠀⣿⡁ mov $57,%rax↵syscall↵cmp $0,%rax↵jne child↵parent:↵mov $61,%rax ⢿⡄⠘⠷⠚⠋⠀ mov $-1,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall↵jmp parent↵child: ⠈⠳⣄⠀⠀⠀⠀ mov $59,%rax↵mov $rc,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall
