Package: debspawn Version: 0.4.1-1 Severity: normal Hi,
when I have a package that doesn't build by itself. I then repeat the build with --interact, see the build fail again, and get a shell. I fix the issue, do fakeroot debian/rules binary, get a package. I then Ctrl-D out of the shell, the container is destroyed and /var/lib/debfoster/result is empty. Work lost. debspawn should look whether packages were created during the debspawn build run even if --interact was given and not throw them away. Greetings Marc -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.11.11-zgsrv20080 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debspawn depends on: ii debootstrap 1.0.123 ii python3 3.9.2-3 ii python3-toml 0.10.1-1 ii systemd-container 247.3-5 ii zstd 1.4.8+dfsg-2.1 Versions of packages debspawn recommends: ii build-essential 12.9 ii devscripts 2.21.1 Versions of packages debspawn suggests: ii sudo 1.9.5p2-3.0 -- no debconf information
