On Fri, 6 Jun 2025 at 19:59, Theodore Ts'o <[email protected]> wrote: > > On Fri, May 30, 2025 at 03:27:56PM +0100, Luca Boccassi wrote: > > > > autopkgtest on debci has highlighted that the 1.47.3~rc1 version of > > mkfs.ext4 fails when used by systemd-repart, while it works with the > > version in unstable and testing: > > Hi, I'm having a lot of trouble trying to replicate the failure. > > autopkgtest is unfortunately, *not* obvious. The replication > instructions mention "<preferred autopkgtest runner config>" but > instructions for how to do this is hard to come by. > > I had a schroot which is suitable for use by sbuild, but when I try to > use it, it blows up with an "su: Authentication failure". > > <tytso@trampoline> {/tmp/systemd-257.6} > 1210% autopkgtest -B --test-name upstream . -- autopkgtest-virt-schroot > sid-amd64-sbuild > autopkgtest [14:52:00]: starting date and time: 2025-06-06 14:52:00-0400 > autopkgtest [14:52:00]: version 5.49 > autopkgtest [14:52:00]: host trampoline; command line: /bin/autopkgtest -B > --test-name upstream . -- autopkgtest-virt-schroot sid-amd64-sbuild > autopkgtest [14:52:00]: testbed dpkg architecture: amd64 > autopkgtest [14:52:00]: testbed apt version: 2.9.30 > autopkgtest [14:52:00]: @@@@@@@@@@@@@@@@@@@@ test bed setup > autopkgtest [14:52:00]: testbed release detected to be: None > autopkgtest [14:52:00]: testbed running kernel: Linux 6.12.27-amd64 #1 SMP > PREEMPT_DYNAMIC Debian 6.12.27-1 (2025-05-06) > autopkgtest [14:52:00]: @@@@@@@@@@@@@@@@@@@@ unbuilt-tree . > su: Authentication failure > blame: . > badpkg: rules extract failed with exit code 1 > autopkgtest [14:52:01]: ERROR: erroneous package: rules extract failed with > exit code 1 > > Looking at the systemd's debian/test/upstream it appears to install an > external third party github repository, https://github.com/systemd/mkosi > but trying to figure out what the *heck* it is doing is... hard. > > Can you perhaps give me some reproduction instructions that even a > kernel developer can follow? Many thanks!! > > Ideally, just a simple mke2fs command so I can see what systemd-repart > is doing. It's just not obvious....
Unfortunately I don't know how to get a manual command that shows the same error. I guess the content of the full debian sid root directory being copied in the ext4 is what triggers the issue, as a naive run with some local directory as sources doesn't work. If you are not familiar with autopkgtest, it's best to use qemu as a runner. You can use autopkgtest-build-qemu to build a sid image: autopkgtest-build-qemu sid /path/to/autopkgtest-sid.img And then you can run the test after placing the new locally built or downloaded from experimental e2fsprogs packages in /path/to/pkgs/dir/ : autopkgtest --test-name upstream -B . /path/to/pkgs/dir/ -- autopkgtest-virt-qemu --cpus 4 --ram-size 8192 /path/to/autopkgtest-sid.img
