Control: tags -1 unreproducible Control: close -1 TL;DR: I have just spent some time to reproduce this with official debian images and cannot reproduce this, hence closing as unactionable.
- Download netinst arm64 weekly testing snapshot from https://cdimage.debian.org/cdimage/weekly-builds/arm64/iso-cd/ - install in an aarch64 VM using virt-manager and run in qemu - go through the installation process selecting all default options - boot into installed VM root@vm-aarch64:~# ls -l / total 56 lrwxrwxrwx 1 root root 7 Jan 3 13:39 bin -> usr/bin drwxr-xr-x 4 root root 4096 Jan 3 14:03 boot drwxr-xr-x 18 root root 3180 Jan 3 14:06 dev drwxr-xr-x 68 root root 4096 Jan 3 14:06 etc drwxr-xr-x 3 root root 4096 Jan 3 14:03 home lrwxrwxrwx 1 root root 7 Jan 3 13:39 lib -> usr/lib drwx------ 2 root root 16384 Jan 3 13:38 lost+found drwxr-xr-x 3 root root 4096 Jan 3 13:38 media drwxr-xr-x 2 root root 4096 Jan 3 13:39 mnt drwxr-xr-x 2 root root 4096 Jan 3 13:39 opt dr-xr-xr-x 182 root root 0 Jan 3 14:05 proc drwx------ 4 root root 4096 Jan 3 14:10 root drwxr-xr-x 19 root root 540 Jan 3 14:10 run lrwxrwxrwx 1 root root 8 Jan 3 13:39 sbin -> usr/sbin drwxr-xr-x 2 root root 4096 Jan 3 13:39 srv dr-xr-xr-x 13 root root 0 Jan 3 14:05 sys drwxrwxrwt 8 root root 160 Jan 3 14:10 tmp drwxr-xr-x 11 root root 4096 Jan 3 13:39 usr drwxr-xr-x 11 root root 4096 Jan 3 14:06 var root@vm-aarch64:~# uname -a Linux vm-aarch64 6.12.6-arm64 #1 SMP Debian 6.12.6-1 (2024-12-21) aarch64 GNU/Linux root@vm-aarch64:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux trixie/sid" NAME="Debian GNU/Linux" VERSION_CODENAME=trixie ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Everything looks just as you expect it. For extra safety, I also checked the other official build tool, which is autopkgtest-build-qemu as it's used by debci. - apt install autopkgtest vmdb2 ... - create an image: autopkgtest-build-qemu --architecture arm64 testing autopkgtest-testing-arm64.img - run an autopkgtest and get a shell: autopkgtest --shell --test-name logind -B . -- autopkgtest-virt-qemu --qemu-architecture aarch64 --dpkg-architecture arm64 --cpus 2 --ram-size 4096 autopkgtest-testing-arm64.img root@host:~# ls -l / ls -l / total 60 lrwxrwxrwx 1 root root 7 Nov 22 14:40 bin -> usr/bin drwxr-xr-x 4 root root 4096 Jan 3 15:12 boot drwxr-xr-x 14 root root 3080 Jan 3 15:40 dev drwxr-xr-x 57 root root 4096 Jan 3 15:39 etc drwxr-xr-x 3 root root 4096 Jan 3 15:07 home lrwxrwxrwx 1 root root 28 Jan 3 15:01 initrd.img -> boot/initrd.img-6.12.6-arm64 lrwxrwxrwx 1 root root 28 Jan 3 15:01 initrd.img.old -> boot/initrd.img-6.12.6-arm64 lrwxrwxrwx 1 root root 7 Nov 22 14:40 lib -> usr/lib drwx------ 2 root root 16384 Jan 3 14:54 lost+found drwxr-xr-x 2 root root 4096 Jan 3 14:55 media drwxr-xr-x 2 root root 4096 Jan 3 14:55 mnt drwxr-xr-x 2 root root 4096 Jan 3 14:55 opt dr-xr-xr-x 149 root root 0 Jan 3 15:40 proc drwx------ 3 root root 4096 Jan 3 14:57 root drwxr-xr-x 18 root root 500 Jan 3 15:43 run lrwxrwxrwx 1 root root 8 Nov 22 14:40 sbin -> usr/sbin drwxr-xr-x 2 root root 4096 Jan 3 14:55 srv dr-xr-xr-x 13 root root 0 Jan 3 15:40 sys drwxrwxrwt 8 root root 4096 Jan 3 15:41 tmp drwxr-xr-x 11 root root 4096 Jan 3 14:55 usr drwxr-xr-x 11 root root 4096 Jan 3 15:38 var lrwxrwxrwx 1 root root 25 Jan 3 15:01 vmlinuz -> boot/vmlinuz-6.12.6-arm64 lrwxrwxrwx 1 root root 25 Jan 3 15:01 vmlinuz.old -> boot/vmlinuz-6.12.6-arm64 root@host:~# uname -a uname -a Linux host 6.12.6-arm64 #1 SMP Debian 6.12.6-1 (2024-12-21) aarch64 GNU/Linux root@host:~# cat /etc/os-release cat /etc/os-release PRETTY_NAME="Debian GNU/Linux trixie/sid" NAME="Debian GNU/Linux" VERSION_CODENAME=trixie ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Same result. Given this alleged issue cannot be reproduced, given the proposed patch is obviously wrong and has been rejected by all upstream maintainers as it breaks other distros and there's no chance it will ever go anywhere, and there's hence nothing really to be done, closing this bug.