On Mon, Feb 01, 2021 at 08:04:42PM +0100, Michael Biebl wrote:
For package maintainers we already have lintian [1]
Yep, much better.
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.
Well, the truly annoying thing is that it warns even for init scripts
disabled, but never removed (sometimes on purpose, sometimes due to package
errors). I discovered a few of them still around since years, and reduced
a bit the noisei by purging.
For sure this system is up since 28th of Jan and dmesg shows
only messages after 30th of Jan currently. So generally, at every restart
of services the syslog is populated with those warnings in good quantity.
Any system upgraded several times and/or used for development will present
tons of this warnings during its life cycle. I know upstream already refused
to take in consideration the possibility of on/off that warns by option. At
least, using debug priority would move those warns to a different log file in
default configuration, not too bad.
--
Francesco P. Lovergine
