Package: debspawn Version: 0.4.1-1 Severity: minor Hi,
I recently tried to use debspawn build building into a slightly outdated image of Debian sid and received a message that dsrun didn't like the "--suite sid" option that was given to it. Updating the image solved the issue for me. I suspect that the "outside" debspawn calls things that are inside the image, and while the outside debspawn was a 0.4.1, the inside was still at 0.4.0 or even older and the interface between the outside and inside code changed with the 0.4.0 to 0.4.1 transition. If my suspicion is true, than this might also apply to images of testing or stable, but without the possibility of just fixing this by updating the image. I understand that this issue is probably hard to fix, but if it doesn't seem possible to just inject the code needed on the inside from the outside at run time (therefore forcing them to be in sync, but possibly introducing python version issues) then there should be at least a more helpful error message than just bombing out with a usage message of an internal tool. Greetings Marc -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.2-zgws1 (SMP w/12 CPU threads) 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.1-1 ii python3-toml 0.10.1-1 ii systemd-container 247.2-2 ii zstd 1.4.5+dfsg-4 Versions of packages debspawn recommends: ii build-essential 12.8 ii devscripts 2.20.5 Versions of packages debspawn suggests: ii sudo 1.9.4p2-1 -- no debconf information
