Hi Michael, That makes sense. I'm working on a few updates to DUE anyway and will roll a fix in with them to reduce churn.
The intent of recommending QEMU (as one would expect) was to allow containers built from different architectures to run locally, so it's probably qemu-user-static since that has to be embedded in the resulting Docker image. I'll do some testing to see if this configuration has any dependencies on a qemu-user installation in the host environment. Thanks! Alex ________________________________ From: Michael Tokarev <m...@tls.msk.ru> Sent: Wednesday, August 25, 2021 5:28 AM To: Debian Bug Tracking System <sub...@bugs.debian.org> Subject: Bug#992947: due wrongly recommends qemu package External email: Use caution opening links or attachments Package: due Version: 2.3.0-2 Severity: important X-Debbugs-Cc: pkg-qemu-de...@lists.alioth.debian.org The "due" package has "qemu" in its Recommends section. This is completely wrong, especially since there's another Recommends for qemu-user-static right next to qemu. In the long past, when qemu first appeared in Debian, there was just one binary package, named qemu, which contained everything. Later on, it has been split at least to full system emulation package (qemu-system) and to user-level emulation package (qemu-user and qemu-user-static), with "qemu" becoming a metapackage and depending on everything. But later on it has become clear that installing whole qemu is useless. So "qemu" package become a dummy empty package with nothing in it and no dependencies. Many bugs has been filed against numerous packages which listed "qemu" in various dependencies, and most of them has been fixed by now. But it seems some new packages emerged which again list qemu as one of dependencies. Please remove it from Recommends. And while doing this, please actually think about what you want to recommend. If you want some user emulation, there are 2 packages - qemu-user and qemu-user-static, both providing the same set of binaries but the latter is compiled statically so it is easier to run things within a foreign chroot. Setting severity to be "important" since a) the thing is clearly wrong and b) I really want to remove qemu binary package from the archive for a long time already and this Recommends doesn't let me do that. Thanks!
