omitted-systemd-service-for-init.d-script

The specified init.d script has no systemd equivalent and the package ships other units.

This typically occurs when a maintainer missed script when adding systemd integration, or a new init script was added in a new upstream version.

Systemd has a SysV init.d script compatibility mode. It provides access to each SysV init.d script as long as there is no native service file with the same name (e.g. /lib/systemd/system/rsyslog.service corresponds to /etc/init.d/rsyslog).

The tag is present in Lintian version 2.114.163. That is the most recent version we know about.

We use semantic versions. The patch number is a commit step indicator relative to the 2.108.0 release tag in our Git repository.

You can find the detection logic for this version at commit a1e47cb. For merge requests, please use the latest version in the Lintian check systemd.

Visibility: error

Renamed from:

systemd-no-service-for-init-script

The following 8 source packages in the archive triggered the tag 9 times (in any Lintian version).

We found 1 overrides. The tag performed 89% of the time.

ceph

radosgw [etc/init.d/radosgw]

diaspora-installer

diaspora-common [etc/init.d/diaspora-common]

exim4

exim4 [etc/init.d/exim4]

fetch-crl

fetch-crl-boot [etc/init.d/fetch-crl-boot]
fetch-crl-cron [etc/init.d/fetch-crl-cron]

munin

munin-tmpfiles [etc/init.d/munin-tmpfiles]

pcp [etc/init.d/pcp]

stunnel4

stunnel4 [etc/init.d/stunnel4]

sudo

sudo-ldap [etc/init.d/sudo-ldap]