commit d59153a5752a894b95fa871e533d4441e67c8d91 Author: Mathias Gibbens <gibmat@debian.org> Date: Wed Mar 12 01:48:15 2025 +0000 Update d/README.Debian to reflect addition of runit scripts commit a158eb813bd62b6956aa81156b43897703c4d6f0 Author: Mathias Gibbens <gibmat@debian.org> Date: Wed Mar 12 01:45:44 2025 +0000 Update minimum required version of lxcfs to ensure its runit scripts will be available commit b51ea60b7ff2e42e297b8c4a3b2bb72ba2d18574 Author: Mathias Gibbens <gibmat@debian.org> Date: Wed Mar 12 01:41:05 2025 +0000 Update d/changelog and d/copyright to reflect runit script additions commit 073e43d752e175385dd799f190833496d796508f Merge: 364deb96 9340dbae Author: Mathias Gibbens <gibmat@debian.org> Date: Wed Mar 12 01:37:22 2025 +0000 Merge branch 'runitsupport' into 'debian/sid' Runit support for Incus (Closes: 1084990). See merge request go-team/packages/incus!1 commit 9340dbae9100cee09b4e89d0c98fe076fa2b4ced Author: Martin Steigerwald <martin@lichtvoll.de> Date: Sun Mar 2 14:51:49 2025 +0100 Runit support for Incus (Closes: 1084990). All files are licensed under Apache-2. Based on the Systemd unit and the init script, with the omission that is does not create "/var/log/incus" on each startup as that directory appears to be created at package installation. Logs for Incus itself will be in "/var/log/runit/incus/current" regardless of the setting in "/etc/default/incus". I documented this there. Runit support does not need the "incus-startup" service. Thus I made the init script stop in case Runit is running. Thanks to Lorenzo for this. This is still the legacy way of using dh_runit such as used in "openssh-server" package. I am willing to provide a merge request to change it to the new way which goes through "/usr/share/runit/sv" instead of installing the service directory directly into "/etc/sv" whenever it becomes available to use in this context. Thanks to Lorenzo, Andrew and Mathias for review!
Among the 7 debian patches available in version 6.0.3-4 of the package, we noticed the following issues:
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.