Your message dated Wed, 3 Nov 2021 09:43:22 +0300
with message-id <[email protected]>
and subject line Re: Bug#998341: qemu-system-common: qemu in bullseye-backports
is incompatible with bullseye libvirt
has caused the Debian Bug report #998341,
regarding qemu-system-common: qemu in bullseye-backports is incompatible with
bullseye libvirt
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.)
--
998341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998341
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-common
Version: 1:5.2+dfsg-11
Severity: normal
X-Debbugs-Cc: [email protected]
I am maintaining Debian support in OpenStack Kolla project. We are
building container images with OpenStack components and provide way to
deploy whole OpenStack from them.
As we have new release cycle now I looked into possible package
upgrades. Newer QEMU in bullseye-backports got my intention.
Then I tried to install it:
root@puchatek /]# apt-get install --no-install-recommends libvirt-clients
libvirt-daemon-system qemu-block-extra qemu-system -t bullseye-backports
libvirt-daemon
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
qemu-system-common : Breaks: libvirt-daemon (< 7.2.0-1) but 7.0.0-3 is to be
installed
E: Unable to correct problems, you have held broken packages.
So it looks like I have to stay with previous version (libvirt maintainer was
never fan of backporting libvirt).
-- System Information:
Debian Release: 11.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.14.0-0.bpo.2-arm64 (SMP w/16 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qemu-system-common depends on:
ii libaio1 0.3.112-9
ii libc6 2.31-13+deb11u2
ii libcap-ng0 0.7.9-2.2+b1
ii libgbm1 20.3.5-1
ii libglib2.0-0 2.66.8-1
ii libgnutls30 3.7.1-5
ii libnettle8 3.7.3-1
ii libpixman-1-0 0.40.0-1
ii libseccomp2 2.5.1-1
pn liburing1 <none>
pn libvirglrenderer1 <none>
ii zlib1g 1:1.2.11.dfsg-2
qemu-system-common recommends no packages.
qemu-system-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
03.11.2021 00:39, Marcin Juszkiewicz wrote:
W dniu 02.11.2021 o 22:26, Michael Tokarev pisze:
What do you want us to do here?
I know full well that libvirt in buster is too old for new qemu.
I don't have enough experience to backport libvirt (I never ever
used it myself). Even if I had such experience, what I should do
with this bugreport?
You are right. I am forgetting that there are people using qemu directly.
Well.. you're definitely not the only one :) This happens quite often.
I use qemu for many years - since before libvirt gained support for it -
and I never used libvirt so far.
...
So I don't see a way to deal with this bugreport.
Close it please. Sorry for that.
Doing this right now.
I feel sorry for the ones who want a backport of a more recent libvirt
to work with current backport of qemu. But the thing is that I don't
know how to deal with libvirt, and don't think it's possible to do
"libvirt backport" within qemu, either :)
Thanks!
/mjt
--- End Message ---
