Your message dated Sat, 26 Oct 2024 11:19:18 +0000
with message-id <[email protected]>
and subject line Bug#1086026: fixed in libguestfs 1:1.52.2-5
has caused the Debian Bug report #1086026,
regarding please fine-tune qemu-system package dependencies
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1086026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086026
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libguestfs
Version: 1:1.52.2-4
Severity: normal
Tags: patch
X-Debbugs-Cc: [email protected]
Historically, qemu grouped various qemu-system-ARCH binaries
into a few packages, providing a package for an architecture
family, and qemu-system-misc package for all the rest. This
grouping has been changed a few times in the past already.
libguestfs currently reflects this qemu-system architecture
grouping in its control file in the Depends: field.
With version 9.1.1 of qemu debian packages, this grouping
has been changed once more, by introducing 2 new architecture
families and 2 new packages - riscv and s390x, making every
debian release architectures to be in their own qemu package.
These architectures were part of qemu-system-misc package
before.
However this broke libguestfs, since it relies on qemu-system-misc
for riscv and s390 binaries, which are not there anymore.
For quite some time, qemu provides virtual packages named after
the executable/binary name, - eg, there's a virtual package
qemu-system-riscv64, which were provided by qemu-system-misc
before and now it is provided by qemu-system-riscv. Ditto
for qemu-system-s390x (which is now its own non-virtual
package).
Usually, I'd suggest to depend on particular qemu binary
name which is used, eg:
Depends: qemu-system-riscv64
But in the case of libguestfs, which has to list such dependency
for every architecture it builds for, maybe there's an easier
approach which can be implemented with the help from qemu side.
There was a talk for qemu to provide qemu-system-for-host of
the right architecture - which will depend on the right qemu
package depending on what the host arch is.
In a similar way, qemu can provide virtual package named, eg,
qemu-system-native, selecting the rigth qemu-system-foo for the
native architecture (qemu-system-mips for mips64el, etc).
This is an RFC/RFD. But for now, I'm providing a tiny patch
for libguestfs d/control, to replace qemu-system-misc dependency
for riscv64 and s390x cases with actual architecture libguestfs
expects from qemu. This change will work with either old or new
qemu packages, but the list in Depends becomes non-uniform: for
some architectures it is qemu package name (qemu-system-x86),
while for other architectures it is virtual qemu package name
(qemu-system-riscv64). So this change will make things work
again, but it is kinda ugly in this way.
Thanks,
/mjt
--- debian/control.orig 2024-10-07 16:21:04.000000000 +0300
+++ debian/control 2024-10-25 11:44:35.382756399 +0300
@@ -25,7 +25,8 @@
gperf, libxml2-utils,
qemu-system-arm [armel armhf arm64],
qemu-system-mips [mips mipsel mips64 mips64el],
- qemu-system-misc [s390x riscv64],
+ qemu-system-s390x [s390x],
+ qemu-system-riscv64 [riscv64],
qemu-system-ppc [powerpc powerpcspe ppc64 ppc64el],
qemu-system-sparc [sparc sparc64],
qemu-system-x86 [i386 amd64],
@@ -188,7 +189,8 @@
supermin (>= 5.2.2-4~),
qemu-system-arm [armel armhf arm64],
qemu-system-mips [mips mipsel mips64 mips64el],
- qemu-system-misc [s390x riscv64],
+ qemu-system-s390x [s390x],
+ qemu-system-riscv64 [riscv64],
qemu-system-ppc [powerpc ppc64 ppc64el],
qemu-system-sparc [sparc],
qemu-system-x86 [i386 amd64],
--- End Message ---
--- Begin Message ---
Source: libguestfs
Source-Version: 1:1.52.2-5
Done: Hilko Bengen <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libguestfs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hilko Bengen <[email protected]> (supplier of updated libguestfs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 26 Oct 2024 12:47:48 +0200
Source: libguestfs
Architecture: source
Version: 1:1.52.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers
<[email protected]>
Changed-By: Hilko Bengen <[email protected]>
Closes: 1086026
Changes:
libguestfs (1:1.52.2-5) unstable; urgency=medium
.
* Tweak qemu-system-* dependencies.
Thanks to Michael Tokarev (Closes: 1086026)
Checksums-Sha1:
6a5d710133e964f01221b4996667fdc40482391a 6988 libguestfs_1.52.2-5.dsc
ebf62ed52c06ca437153d40d88c095282aeb2363 42928
libguestfs_1.52.2-5.debian.tar.xz
f9db6e3819d508ada174ff68a9449e6ab3d7716e 26573
libguestfs_1.52.2-5_source.buildinfo
Checksums-Sha256:
3c382bb5459468b0d970448d1c6e5fe7bd56d7194cc098fb70761da5a9e4e6f0 6988
libguestfs_1.52.2-5.dsc
37b23c8347b9d36bf5f9d01e45382ff31f4d71858d93e04da7248d5a18371497 42928
libguestfs_1.52.2-5.debian.tar.xz
e359653529cfbae1eddc9d9ccd55d93837b4c3ce2bb5854021d8ded3bdf6e615 26573
libguestfs_1.52.2-5_source.buildinfo
Files:
849118422815e5e53368fd6e85992d41 6988 libs optional libguestfs_1.52.2-5.dsc
0eb5021ea0890de0c6843fa544042efe 42928 libs optional
libguestfs_1.52.2-5.debian.tar.xz
5077bd0b26a6c455aea9732e762ac4c5 26573 libs optional
libguestfs_1.52.2-5_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmccy2MACgkQdbcQY1wh
On6VCxAAl6kVanelYJIEj1jVqKJx38hz1CqW71w0vblvqtauHHj114i8FQvaWNn+
bUOB1xZlJKmZunTajTdDfHnY1LvgdjXH94qhOwymNY1hQEt+z0W8eXMvKy6e1F4E
FAqFJ5WD3ZnrrlLd7jOzkOLXTxoL3erPHxIfxLjsh+hNl1RbdLjMnkIqlKuuKqDH
Tp127rJAv6JCAIs/cgkp++y8WLFLqHAt3AyNreOy+A2AAVy+5/zH8LdoUGbwFOLf
1HbaPhx5v/59mC6bxqpzWw7wK3qUxHCzp+1SOX4mBFLu+8PyRBNYrsIBYcA6AXl3
99sXkka0JluqFSVeBS+JiesNi9JLg8IPNeMQXxMxApysb/v2qPQ+q4IoUkd4L7zB
aSBxqiMnpecWSYaN0DbBCjLADh3e7qgYwGcCkeu87znrPy2vTYOee8jbNzycfZBG
1GkGpk40dYEXhIvzaFwFFoSHB/veCjxJkIElAfBiQvJBlP/tZIdm6z0LKlZ9WT3C
d3T/0wUpTvUPmR3s2hQoXG03l7LAskHigtBjNHbRcHoUvS+wcdQEDZjhjkVdViGf
DYIoFGrz1wgch3lJ5ZSgpfMsgaHhbcDjjVrUG+uSUTmuwOiYXtDV7V3Wd2k+3pKh
GiETr2ySoRCXVB4ULyGJdWjZS6Bbe5uou/204Fe1DC/0cxCGmYQ=
=EUMz
-----END PGP SIGNATURE-----
pgpcYo2dODjog.pgp
Description: PGP signature
--- End Message ---
