Dear libvirt maintainers,

libvirt-daemon-driver-qemu is hardly installable for runit-init users
because it has a dependency expressed as

systemd-container | sysvinit-core

runit conflicts with sysvinit-core for obvious reason; systemd-container
is technically insallable under runit-init (as it would be under sysvinit-core)
but doing so removes elogind and then everything related to policykit
stops working.. [1]

Runit has an emulation of sysvinit scripts for when there is no
runit-init support, so if it works with sysvinit it should also work
with runit-init: please consider to change the dependency into

systemd-container | sysvinit-core | runit-init

Best Regards,
Lorenzo

[1]
# apt-get install libvirt-daemon-driver-qemu
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Solving dependencies... Done
The following packages were automatically installed and are no longer required:
 [snip, long list]
  r-cran-zeallot vcdimager xwaylandvideobridge
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libnss-mymachines libvirt-common libvirt-daemon-log libvirt-l10n libvirt0 passt seatd swtpm-tools systemd
  systemd-container systemd-cryptsetup
Suggested packages:
  numad apparmor trousers systemd-homed systemd-userdbd systemd-boot systemd-resolved systemd-repart
  libtss2-tcti-device0 polkitd
The following packages will be REMOVED:
  dolphin-plugins drkonqi elogind frameworkintegration gparted k3b k3b-extrathemes kaffeine kamera kate
  kde-config-cddb kde-config-cron kde-config-screenlocker kde-style-breeze-qt5 kde-style-oxygen-qt5
  kde-window-manager kdenetwork-filesharing kgamma5 khotkeys kinit kinit-dev kio kmplayer kwalletmanager
  kwin-common kwin-wayland kwin-x11 kwrite libkf5auth5 libkf5authcore5 libkf5bookmarks5 libkf5configwidgets5
  libkf5iconthemes5 libkf5kdelibs4support5-bin libkf5kdelibs4support5t64 libkf5kiocore5 libkf5kiofilewidgets5
  libkf5kiogui5 libkf5kiowidgets5 libkf5mediaplayer5 libkf5newstuffcore5 libkf5parts5 libkf5plasma5 libkf5style5
  libkf5textwidgets5 libkf5xmlgui5 libkf6authcore6 libkf6texteditor-bin libkf6texteditor-katepart
  libkf6texteditor6 libksysguard-bin liboxygenstyle5-5 liboxygenstyle5-6 libpam-elogind libplasma5support6
  libpolkit-qt5-1-1 libpolkit-qt6-1-1 libpowerdevilcore2 libprocesscore10 libweather-ion7 lightdm lxqt-panel
  lxqt-policykit lxqt-powermanagement modemmanager opentmpfiles pkexec plasma-systemmonitor plasma-workspace
  polkit-kde-agent-1 polkitd powerdevil print-manager qml-module-org-kde-newstuff qml6-module-org-kde-ksysguard
  qml6-module-org-kde-plasma-plasma5support slim systemd-standalone-sysusers systemsettings
  xdg-desktop-portal-kde
The following NEW packages will be installed:
  libnss-mymachines libvirt-common libvirt-daemon-driver-qemu libvirt-daemon-log libvirt-l10n libvirt0 passt
  seatd swtpm-tools systemd systemd-container systemd-cryptsetup
0 upgraded, 12 newly installed, 80 to remove and 38 not upgraded.
Need to get 10.7 MB of archives.
After this operation, 119 MB disk space will be freed.
Do you want to continue? [Y/n]

The change you're suggesting makes sense, but I'd like to try the
setup for myself before committing to it. In your experience, is the
information found at

https://wiki.debian.org/Init#Changing_the_init_system_-_at_installation_time

accurate when it comes to switching from systemd to runit? I've
successfully used it in the past to test SysV and OpenRC
compatibility.

Thanks.

Hi Andrea,

thanks :)

mostly, but it misses a step (the removal of the "init" metapackage):
I have an autopkgtest for the init switch that has all the commands
(but it does not account for elogind as it's an headless container)

see
https://salsa.debian.org/debian/runit/-/blob/master/debian/tests/init-switch?ref_type=heads
around line 51 and 52

Lorenzo