On Sat, 30 Jan 2021 19:01:54 +0100 Francesco Paolo Lovergine <[email protected]> wrote: > Package: systemd > Version: 247.2-5 > Severity: wishlist > Tags: upstream > > This is the result of rebooting one of my boxes with bullseye: > > $ sudo dmesg|grep 'lacks a native systemd'|wc -l > 463 > > It gives the same message for tons of init scripts and even for scripts that are > there for historical reasons due to packages never purged. While I could > undestand the idea of trying to encourage the maintainers to provide also > unit files, on the users side this is a nice way to encourage haters of > systemd and the whole distribution.
For package maintainers we already have lintian [1]. Unfortunately, we can't differentiate between SysV init scripts provided by Debian packages vs local ones (and no, running dpkg -S from sysv-generator is not an option). So personally, I consider the warnings from the sysv-generator more relevant actually for locally written SysV init scripts and the ones provided by 3rd party packages. Eventually, we are going to remove SysV support in systemd. This won't happen in bullseye and maybe not bookworm, but we won't keep support for SysV init scripts forever. So people should be made aware of this, and ideally, they have more then one release cycle to prepare for this. So I'm undecided whether to remove (or downgrade to debug) this warning or not. What do you suggest? For a regular bullseye installation, I wouldn't actually expect that much noise as you see. Michael [1] https://lintian.debian.org/tags/missing-systemd-service-for-init.d-script.html
signature.asc
Description: This is a digitally signed message part
