Source: snek Version: 1.9-3 Severity: normal Tags: patch X-Debbugs-Cc: pkg-qemu-de...@lists.alioth.debian.org
qemu-system packages has been grouped in several packages, and this grouping changed a few times in the past. This same thing happened again with qemu 9.1.1 debian packages - I split qemu-system-riscv package out of qemu-system-misc. Since this time, snek autopkgtests fails because snek depends on qemu-system-misc for the riscv qemu binaries, which aren't there anymore. In order to simplify dependencies like this, for quite some time qemu system packages provide virtual packages named after binaries they contain. If you rely on particular qemu architecture (be it upstream qemu or debian variant of this name), for example, if you run qemu-system-riscv32, you can use this exact name in the Depends: field, and it will be resolved automatically no matter which package actually provides this binary. This worked before 9.1.1 (the riscv32 binary were provided by qemu-system-misc package) and works now with 9.1.1 (this binary is now provided by the new qemu-system-riscv package). A trivial patch to implement this is below. For the arm case, the binary name provided is the same as the package name, so no changes is needed there. Thanks, /mjt --- debian/tests/control.orig 2023-09-27 21:27:47.000000000 +0300 +++ debian/tests/control 2024-10-25 11:23:50.495133807 +0300 @@ -1,2 +1,2 @@ Test-Command: make SNEK_NATIVE=/usr/bin/snek SNEK_ARM=/usr/share/snek/snek-arm SNEK_RISCV=/usr/share/snek/snek-riscv -C test check -Depends: @, qemu-system-arm, qemu-system-misc, gcc +Depends: @, qemu-system-arm, qemu-system-riscv32, gcc
