docs/manpages/libvirt-guests.rst | 4 2 + 2 - 0 !
tools/libvirt-guests.sh.in | 15 7 + 8 - 0 !
2 files changed, 9 insertions(+), 10 deletions(-)

 debianize libvirt-guests

src/security/apparmor/libvirt-lxc | 7 7 + 0 - 0 !
src/security/apparmor/libvirt-qemu | 7 7 + 0 - 0 !
2 files changed, 14 insertions(+)

 apparmor_profiles_local_include

Include local apparmor profile

tools/vsh.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 use sensible-editor by default

It is the reasonable default for Debian.

src/remote/libvirtd.service.in | 2 0 + 2 - 0 !
1 file changed, 2 deletions(-)

 drop inter-package also= lines from libvirtd.service

systemctl handles these lines gracefully even when the
corresponding unit is not present, e.g. because the daemon-lock
package is not installed, but deb-systemd-helper doesn't. As a
temporary workaround until this limitation is addressed, drop
the lines triggering the failure.

Note that we would technically only need to drop the reference
to virtlockd.socket, since the daemon-log package is a hard
dependency of the daemon package and thus we know that
virtlogd.socket is always going to be present, but being more
aggressive for consistency's sake seems preferable.

Bug-Debian: https://bugs.debian.org/1082939
Bug-Debian: https://bugs.debian.org/1091519

src/remote/libvirtd.service.in | 4 0 + 4 - 0 !
1 file changed, 4 deletions(-)

 drop handling of secret encryption from libvirtd.service

It breaks libvirtd completely if the secret driver is not
installed, which is a bit harsh. Until the issue is addressed,
leave the functionality out entirely. The secret driver will
handle this gracefully by simply continuing to store secrets
unencrypted, as it had been doing before 12.1.0.

Bug: https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/message/743FQZ6LGNYEREWOSTJJXHVE67GYBAXU/

src/qemu/libvirt-qemu.sysusers.conf | 7 4 + 3 - 0 !
1 file changed, 4 insertions(+), 3 deletions(-)

 customize sysusers.d file