Control: tag -1 + moreinfo

02.11.2021 19:47, Marcin Juszkiewicz wrote:
Package: qemu-system-common
Version: 1:5.2+dfsg-11
Severity: normal
X-Debbugs-Cc: marcin.juszkiew...@linaro.org

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.

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?

Should I maybe remove the qemu backport and hence close this bugreport?
More recent qemu is definitely useful on buster - for me and for some
other people as well, so I don't quite want to remove it from bpo.

So I don't see a way to deal with this bugreport.

Thanks,

/mjt

Reply via email to