Package: sbuild
Version: 0.78.1-2
Severity: normal
I started to try out --chroot-mode=qemu and it's fantastic!
When attempting to investigate a failed build, it seems that
--build-failed-commands '%SBUILD_SHELL' does not work. There is no
reaction to input.
This can be reproduced eg by adding an exit 1 somewhere in debian/rules
of src:librscode (a very small package with no dependencies other than
debhelper).
The test bed was a simple VM generated with autopkgtest 5.11:
# autopkgtest-build-qemu sid autopkgtest-sid.img
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-0.bpo.2-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sbuild depends on:
ii adduser 3.118
ii libsbuild-perl 0.78.1-2
ii perl 5.28.1-6
Versions of packages sbuild recommends:
ii autopkgtest 5.11
ii debootstrap 1.0.115~bpo10+1
ii schroot 1.6.10-6+b1
Versions of packages sbuild suggests:
pn deborphan <none>
ii e2fsprogs 1.45.3-3~bpo10+1
ii kmod 26-1
ii wget 1.20.1-1.1
