Your message dated Sun, 14 Feb 2021 17:59:42 +0300
with message-id <[email protected]>
and subject line Re: Bug#981475: qemu-system-common: Upgrading the backports
version of qemu-system-common removed qemu-system-x86
has caused the Debian Bug report #981475,
regarding qemu-system-common: Upgrading the backports version of
qemu-system-common removed qemu-system-x86
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.)
--
981475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981475
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-common
Version: 1:5.2+dfsg-3~bpo10+1
Severity: important
Dear Maintainer,
I did apt-get upgrade and noticed that qemu-system-common and qemu-system-x86
were not included in the normal upgrade. My Qemu x86/x86_64 VMs did not work
after that either. I think it was due to some library or linking related
errors. I had installed Qemu from the backports some time ago.
So I did dist-upgrade, and it removed qemu-system-x86 while upgrading qemu-
system-common. Any x86/x86_64 Qemu VM was of course unusable after this.
I installed qemu-system-x86 manually from the backports, and it seems to work
normally. Only this error is given when starting it, but it's not apparently
serious:
=====================
qemu-system-x86_64: warning: dbind: Couldn't register with accessibility bus:
Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.
=====================
I attached the last console output of apt-get (truncated and translated to
english, btw, I think it's not necessarily a good decision to localize system
utilities).
-- System Information:
Debian Release: 10.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8),
LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages qemu-system-common depends on:
ii libaio1 0.3.112-3
ii libc6 2.28-10
ii libcap-ng0 0.7.9-2
ii libgbm1 18.3.6-2+deb10u1
ii libglib2.0-0 2.58.3-2+deb10u2
ii libgnutls30 3.6.7-4+deb10u5
ii libnettle6 3.4.1-1
ii libpixman-1-0 0.36.0-1
ii libseccomp2 2.3.3-4
ii liburing1 0.7-3~bpo10+1
ii libvirglrenderer0 0.7.0-2
ii zlib1g 1:1.2.11.dfsg-1
qemu-system-common recommends no packages.
qemu-system-common suggests no packages.
-- no debconf information
*** /home/usrr/qemubug1.txt
$ sudo apt-get dist-upgrade
...
The following packages were automatically installed and are no longer required:
libbrlapi0.6 libcacard0 libcapstone3 libdaxctl1 libfdt1 libndctl6 libpmem1
libslirp0 libspice-server1 libusbredirparser1 libvdeplug2 libvirglrenderer0
libxencall1 libxendevicemodel1 libxenevtchn1 libxenforeignmemory1
libxengnttab1 libxenmisc4.11 libxenstore3.0 libxentoolcore1 libxentoollog1
qemu-system-common qemu-system-data seabios
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
qemu-system-x86
The following packages will be upgraded:
qemu-system-common
1 to upgrade, 0 new, 1 to remove and 0 not upgraded.
Need to download 1 646 kB.
After this, 33,9 MB will be freed.
...
Download:1 http://ftp.de.debian.org/debian buster-backports/main amd64 qemu-
system-common amd64 1:5.2+dfsg-3~bpo10+1 [1 646 kB]
...
Removing qemu-system-x86 (1:5.0-14~bpo10+1) ...
(Reading database ... 359300 files and directories currently installed.)
Preparing to unpack .../qemu-system-common_1%3a5.2+dfsg-3~bpo10+1_amd64.deb ...
Unpacking qemu-system-common (1:5.2+dfsg-3~bpo10+1) over (1:5.0-14~bpo10+1) ...
Setting up qemu-system-common (1:5.2+dfsg-3~bpo10+1) ...
Processing triggers for man-db (2.8.5-2) ...
$sudo apt-get install -t buster-backports qemu-system-x86
...
The following package was automatically installed and is no longer required:
libcapstone3
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
libcapstone4 libfdt1
Suggested packages:
samba vde2
The following NEW packages will be installed:
libcapstone4 qemu-system-x86
The following packages will be upgraded:
libfdt1
...
Download:1 http://ftp.de.debian.org/debian buster-backports/main amd64
libcapstone4 amd64 4.0.2-3~bpo10+1 [559 kB]
Download:2 http://ftp.de.debian.org/debian buster-backports/main amd64 libfdt1
amd64 1.6.0-1~bpo10+1 [21,1 kB]
Download:3 http://ftp.de.debian.org/debian buster-backports/main amd64 qemu-
system-x86 amd64 1:5.2+dfsg-3~bpo10+1 [8 143 kB]
...
Selecting previously unselected package libcapstone4:amd64.
(Reading database ... 359321 files and directories currently installed.)
Preparing to unpack .../libcapstone4_4.0.2-3~bpo10+1_amd64.deb ...
Unpacking libcapstone4:amd64 (4.0.2-3~bpo10+1) ...
Preparing to unpack .../libfdt1_1.6.0-1~bpo10+1_amd64.deb ...
Unpacking libfdt1:amd64 (1.6.0-1~bpo10+1) over (1.4.7-3) ...
Selecting previously unselected package qemu-system-x86.
Preparing to unpack .../qemu-system-x86_1%3a5.2+dfsg-3~bpo10+1_amd64.deb ...
Unpacking qemu-system-x86 (1:5.2+dfsg-3~bpo10+1) ...
Setting up libfdt1:amd64 (1.6.0-1~bpo10+1) ...
Setting up libcapstone4:amd64 (4.0.2-3~bpo10+1) ...
Setting up qemu-system-x86 (1:5.2+dfsg-3~bpo10+1) ...
--- End Message ---
--- Begin Message ---
On Sun, 31 Jan 2021 20:27:25 +0200 johan <[email protected]> wrote:
Package: qemu-system-common
Version: 1:5.2+dfsg-3~bpo10+1
Severity: important
Dear Maintainer,
I did apt-get upgrade and noticed that qemu-system-common and qemu-system-x86
were not included in the normal upgrade. My Qemu x86/x86_64 VMs did not work
after that either. I think it was due to some library or linking related
errors. I had installed Qemu from the backports some time ago.
This is how apt & backports works. If you install something from bpo, and a
_new_
version of that something requires some other package from bpo, apt will not
upgrade it by default, unless you specify -t buster-backports explicitly,
because the default release from which it installs stuff is buster, not
buster-backports.
In this case, the "new-something" required by qemu-5.2+bpo are libcapstone4
and libfdt1 which you can see being installed in your log, when you explicitly
specify stuff to install.
When you added some force (telling apt to DIST-upgrade), it tried its best to
upgrade things to buster without installing new stuff from buster-backports.
Which was removing of qemu-system-x86 (since it now depends on new stuff from
bpo). Apt told you about that (it said which packages it will REMOVE, in all
caps), and you agreed. It can't work out that you need more stuff from bpo.
When you do a dist-upgrade from buster to bullseye, it all will work just as
it should, because apt will be told to install everything from bullseye and
will find all the new dependencies just fine. But in case of backports, you
didn't tell it to search for new deps in bpo (and I don't think there's a
way to do that).
I'm not sure I can consider this a bug in apt, but it definitely is not a
bug in qemu. So closing it there.
Thanks,
/mjt
--- End Message ---
