Bug#931889: package-supports-alternative-init-but-no-init.d-script way too aggressive

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#931889: package-supports-alternative-init-but-no-init.d-script way too aggressive

Michael Biebl-3
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.
There are a lot of cases where a service ships a systemd service file
but not a sysv init script:
- D-Bus activated services
- one sysv init script, multiple systemd service files
- sysv init script named differently then systemd service file (but
  shipping a Alias symlink)
- crontab vs systemd.timer/systemd.service

Given the high probability of false positives, please consider
downgrading that lintian check to informal or even pedantic.

Thanks,
Michael


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lintian depends on:
ii  binutils                       2.32.51.20190707-1
ii  bzip2                          1.0.6-9.2
ii  diffstat                       1.62-1
ii  dpkg                           1.19.7
ii  dpkg-dev                       1.19.7
ii  file                           1:5.35-4
ii  gettext                        0.19.8.1-9
ii  gpg                            2.2.13-2
ii  intltool-debian                0.35.0+20060710.5
ii  libapt-pkg-perl                0.1.36+b1
ii  libarchive-zip-perl            1.64-1
ii  libcapture-tiny-perl           0.48-1
ii  libcgi-pm-perl                 4.40-1
ii  libclass-accessor-perl         0.51-1
ii  libclone-perl                  0.41-1+b1
ii  libdigest-sha-perl             6.02-1+b1
ii  libdpkg-perl                   1.19.7
ii  libemail-valid-perl            1.202-1
ii  libfile-basedir-perl           0.08-1
ii  libio-async-perl               0.72-1
ii  libipc-run-perl                20180523.0-1
ii  liblist-compare-perl           0.53-1
ii  liblist-moreutils-perl         0.416-1+b4
ii  libmoo-perl                    2.003004-2
ii  libparse-debianchangelog-perl  1.2.0-13
ii  libpath-tiny-perl              0.108-1
ii  libtext-levenshtein-perl       0.13-1
ii  libtimedate-perl               2.3000-2
ii  libtry-tiny-perl               0.30-1
ii  libtype-tiny-perl              1.004004-1
ii  liburi-perl                    1.76-1
ii  libxml-simple-perl             2.25-1
ii  libyaml-libyaml-perl           0.76+repack-1
ii  man-db                         2.8.5-2
ii  patchutils                     0.3.4-2
ii  perl                           5.28.1-6
ii  t1utils                        1.41-3
ii  xz-utils                       5.2.4-1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b5

Versions of packages lintian suggests:
pn  binutils-multiarch     <none>
ii  libhtml-parser-perl    3.72-3+b3
ii  libtext-template-perl  1.55-1

-- no debconf information

Reply | Threaded
Open this post in threaded view
|

Bug#931889: package-supports-alternative-init-but-no-init.d-script way too aggressive

Francesco Poli (wintermute)
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

attachment0 (849 bytes) Download Attachment