[Pkg-libvirt-maintainers] Bug#1094583: Bug#1094583: libvirt-daemon-driver-qemu: apparmor template missing from filesystem

[Andrea Bolognani]

I think I'm starting to figure out what went wrong.

Looking at the log you shared, we can see this sequence of events:

  Removing libvirt-daemon-system (9.0.0-4+deb12u1) ...

  Preparing to unpack .../libvirt-daemon-driver-qemu_10.7.0-3_amd64.deb ...
  Unpacking libvirt-daemon-driver-qemu (10.7.0-3) over (9.0.0-4+deb12u1) ...

  Setting up libvirt-daemon-driver-qemu (10.7.0-3) ...
  Installing new version of config file /etc/apparmor.d/abstractions/libvirt-qemu ...
  Configuration file '/etc/libvirt/qemu.conf'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
  Installing new version of config file /etc/libvirt/qemu.conf ...

  Selecting previously unselected package libvirt-daemon-system.
  Preparing to unpack .../libvirt-daemon-system_10.7.0-3_amd64.deb ...
  Preparing transfer of config file /etc/apparmor.d/abstractions/libvirt-qemu (from libvirt-daemon-system to libvirt-daemon-driver-qemu) ...
  Preparing transfer of config file /etc/libvirt/qemu.conf (from libvirt-daemon-system to libvirt-daemon-driver-qemu) ...
  Unpacking libvirt-daemon-system (10.7.0-3) ...
  Setting up libvirt-daemon-system (10.7.0-3) ...

For the transfer process to work correctly, we need preinst for the
package that conffiles are being transferred from (in this case
daemon-system) to run before preinst for the package they're being
transferred to (in this case daemon-driver-qemu).

This is supposed to be enforced by the following relationships
included in debian/control:

  Package: libvirt-daemon-driver-qemu
  Breaks: libvirt-daemon-system (<< 10.6.0-2~)
  Replaces: libvirt-daemon-system (<< 10.6.0-2~)

However, as can be seen above, apt decides against configuring
daemon-system before other packages and removes it instead. As a
consequence, the transfer process breaks down.

I need to figure out how to ensure that the various steps happen in
the expected order. I have a couple of ideas, but some
experimentation will be necessary.

Going by the logs, you seem to have Xfce installed on your test
environment. Anything notable about the setup? I'm hoping that by
creating an installation as similar as possible to yours I will be
able to trigger the same upgrade failure... That'd make fixing it
easier.

-- 
Andrea Bolognani <eof at kiyuko.org>
Resistance is futile, you will be garbage collected.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-libvirt-maintainers/attachments/20250202/aa72b58b/attachment.sig>