Hi all,

To raise awareness of the issue, I've now seen at least two
(consecutive) runs of dracut tmpfail on arm64/unstable with something
that looks like an autopkgtest issue. Interestingly [1] and [2] fail at
different points and on amd64 it seems fine.

[1] https://ci.debian.net/packages/d/dracut/unstable/arm64/75875546/
(recycled; but failed at 20-....)
[2] https://ci.debian.net/packages/d/dracut/unstable/arm64/75875546/

745s dracut: Generating /boot/initrd.img-7.2.6+deb14-arm64
757s Setting up qemu-system-common (1:11.1.1+ds-1) ...
757s Setting up linux-image-arm64 (7.2.6-1) ...
757s Setting up qemu-system-arm (1:11.1.1+ds-1) ...
757s Setting up dracut-test (112-6) ...
757s Processing triggers for libc-bin (2.43-6) ...
757s Processing triggers for dracut (112-6) ...
757s update-initramfs: Generating /boot/initrd.img-7.2.6+deb14-arm64
771s autopkgtest [12:33:23]: ERROR: "sh -ec dpkg-query --show -f
'${Package}\t${Version}\n' >
/tmp/autopkgtest.pbknPh/15-busybox-packages.all" failed with stderr "sh:
1: cannot create /tmp/autopkgtest.pbknPh/15-busybox-packages.all:
Directory nonexistent
771s "

retitle: autopkgtest sometimes fails while saving the package list

Hi
Seems like it's not only dracut, but now also seen in iwatch:
https://ci.debian.net/packages/i/iwatch/testing/amd64/75997562/

Paul