Package: vmdb2 Version: 0.22-1 Severity: normal Tags: upstream X-Debbugs-Cc: pkg-raspi-maintain...@lists.alioth.debian.org
"deprecate qemu-debootstrap" is the primary commit message of: https://salsa.debian.org/qemu-team/qemu/-/commit/9899b1723119e57354c5d8e6f68f15ed762bd570 And it change the call to 'debootstrap' itself. I haven't tried whether that would succeed or not. So I'd guess that vmdb2 should deprecate it as well. http://git.liw.fi/vmdb2/commit/vmdb/plugins?id=bc42e2a8e94713dafb4de4546352749354bc80e0 is an upstream commit which does (seem to) add the needed functionality to the debootstrap call and adds a not to the *documentation*, but afaict the qemu-debootstrap plugin is still available and doesn't alert the user of its deprecation. And I think it should, by at least outputting/logging a warning and possibly switching to error/fail (over time?). As I don't think it's actually/fully fixed upstream, I omitted that tag. CC-ing RPi maintainers as I know it uses a qemu-debootstrap step. Cheers, Diederik -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vmdb2 depends on: ii cmdtest 0.32.14.gcdfe14e-2 ii debootstrap 1.0.123 ii e2fsprogs 1.46.2-2 ii kpartx 0.8.5-2 ii parted 3.4-1 ii python3 3.9.2-3 ii python3-jinja2 2.11.3-1 ii python3-yaml 5.3.1-5 ii qemu-utils 1:6.0+dfsg-2exp Versions of packages vmdb2 recommends: ii ansible 2.10.7+merged+base+2.10.8+dfsg-1 ii dosfstools 4.2-1 ii qemu-user-static 1:6.0+dfsg-2exp vmdb2 suggests no packages. -- no debconf information
