On Wed, 2025-10-15 at 16:24:56 +0100, Luca Boccassi wrote: > Control: severity -1 serious > > Dear Maintainer(s) of affected packages, these bugs have been open for > more than 2 years now. Policy was updated to make units mandatory for > system services. The removal of compat with sysv-init scripts from > systemd has been postponed from trixie to forky, but it is now > approaching. In approximately a month's time, this should hit > unstable, if everything goes well. > > Therefore in order to ensure the remaining bugs do not fall through > the cracks I am raising severity again, as there is a very high chance > the affected packages will stop working as intended in about a month's > time in the default setup. > > As already mentioned in the original bug report, if your package is > not intended to work as a systemd service or under systemd at all, > please feel free to downgrade or close+wontifx or anything else as you > see fit. The severity raising is not intended to make anyone support > scenarios they don't wish to support, but simply to ensure attention > is given to the issue, even if just to close+wontfix. Also the bugs > were opened based on Lintian reports, and it is possible that there > might be false positives.
I've reworked the init system support, and split the sysvinit scripts, one per daemon, and switched to best practices for those, and added systemd unit files. I need to test the upgrade path, but otherwise I'm planning on uploading next Monday or so. Regards, Guillem
