On Thu, 11 Jul 2019 23:19:00 +0200 Michael Biebl wrote: > Package: lintian > Version: 2.16.0 > Severity: normal > > Hi, > > in several of my packages I get a lintian error since a few days ago: > package-supports-alternative-init-but-no-init.d-script > All of them false positives.
Hello! I am another package maintainer who has just been bitten by this bug. > There are a lot of cases where a service ships a systemd service file > but not a sysv init script: [...] > - crontab vs systemd.timer/systemd.service In my package (apt-listbugs), I added a systemd timer unit equivalent to the preexisting daily cron job, in response to a lintian complaint (see bug [#927970]). And a systemd timer unit requires a corresponding systemd service unit, but does not implement a daemon. And indeed apt-listbugs does not ship any daemons! Lintian should not complain for something that was added in response to another Lintian complaint! ;-) [#927970]: <https://bugs.debian.org/927970> > > Given the high probability of false positives, please consider > downgrading that lintian check to informal or even pedantic. Not only that, please! The new Lintian check should try hard to be more accurate: for instance, it should look whether there is a corresponding timer unit along with the service unit. If this is the case, it should not emit any complaint at all! I hope this bug can be fixed soon. Thanks for your time. Bye! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpmvgcPSaCkj.pgp
Description: PGP signature
