libvirt (11.1.0-2) experimental; urgency=medium

  As part of the big package reorganization that has been
  implemented in libvirt 10.6.0-2, ownership of several conffiles
  had to be transferred between binary packages.

  As an example, /etc/libvirt/qemu.conf is now owned by
  libvirt-daemon-driver-qemu instead of libvirt-daemon-system.

  Depending on the order in which packages are unpacked and
  configured during the upgrade process, which is something that we
  have limited control over, the old package might still list the
  involved files as "obsolete" conffiles owned by it.

  The following packages might be affected by the issue:

    * libvirt-client
    * libvirt-daemon-system
    * libvirt-daemon-system-sysv
    * libvirt-sanlock

  To check whether a specific package is affected:

    $ dpkg-query --showformat='${Conffiles}\n' \
                 --show libvirt-daemon-system | grep obsolete
    /etc/libvirt/qemu.conf 8da3a97d2d4fe0870a810c7433efef31 obsolete

  To address the issue once detected:

    $ sudo apt reinstall libvirt-daemon-system

  Some files might still show up in the list even after reinstalling
  the package: for example, /etc/libvirt/lxc.conf will end up in
  this situation if you didn't have the libvirt-daemon-driver-lxc
  package installed before upgrading. To finish cleaning up,
  manually delete the remaining files from the system and reinstall
  the package once again.

 -- Andrea Bolognani <eof@kiyuko.org>  Sun, 23 Mar 2025 18:10:38 +0100

libvirt (10.10.0-4) unstable; urgency=medium

  nftables support is now available in the network driver.

  The default backend is still iptables for now, since the nftables
  backend is incompatible with popular software such as Docker and
  ufw (see #1090355 for details). Additionally, the nwfilter driver
  only supports iptables at this time.

  Users for whom these caveats are not relevant can switch to the
  nftables backend by editing /etc/libvirt/network.conf; after doing
  so, they'll be able to safely uninstall the iptables package.

 -- Andrea Bolognani <eof@kiyuko.org>  Fri, 27 Dec 2024 15:33:13 +0100

libvirt (10.6.0-2) experimental; urgency=medium

  The package has been reworked significantly.

  All the various drivers and storage backends come in their own
  separate binary packages now, which makes it possible to install
  exactly as many or as few as desired.

  The system-wide configuration for the libvirtd daemon is no longer
  shipped separately from the daemon itself, as was the case until
  today; the libvirt-daemon package now contains everything
  necessary to run libvirtd as a system daemon.

  The libvirt-daemon-system package still exists, but it's now
  simply a convenient way to install the "typical" libvirt
  deployment consisting of all the components needed to run a
  QEMU-based hypervisor, and it is completely safe to uninstall it
  if you would rather have a more tailored deployment or if QEMU
  is not available on your architecture.

 -- Andrea Bolognani <eof@kiyuko.org>  Sat, 24 Aug 2024 11:01:43 +0200

libvirt (9.6.0-1) unstable; urgency=medium

  Local overrides for AppArmor abstractions are now expected to
  be /etc/apparmor.d/abstractions/libvirt-{qemu,lxc}.d/... instead
  of /etc/apparmor.d/local/abstractions/libvirt-{qemu,lxc}.

  The old locations are still accepted for now, but support for
  them will be dropped in a future release.

 -- Andrea Bolognani <eof@kiyuko.org>  Wed, 02 Aug 2023 21:41:19 +0200
