Package: lintian Version: 2.32.0 Severity: normal To fix #933109, lintian no longer emits package-supports-alternative-init-but-no-init.d-script when there is a .service and .timer pair.
I would like to see this extended to also include a .service and .path pair. Just as with a .timer, if a .path unit is launching a .service unit, we would not expect an equivalent init.d script. Furthermore, in both cases, since the .timer or .path will be triggering the .service, it is completely normal that the .service unit will not have an [Install] section. Most [Install] sections just contain WantedBy, which is to make something (typically the default target) Wants= the .service unit so it starts on bootup. That is not relevant for .service units that are launched by .timer and .path units. So it would be nice if the systemd-service-file-missing-install-key was similarly not emitted in these cases. Here is an example from ntpsec: debian/ntpsec-systemd-netif.path [Unit] Documentation=file:///usr/share/doc/ntpsec/README.Debian.gz#DHCP DefaultDependencies=no [Path] PathChanged=/run/systemd/netif/leases [Install] WantedBy=network-pre.target debian/ntpsec-systemd-netif.service [Unit] Documentation=file:///usr/share/doc/ntpsec/README.Debian.gz#DHCP [Service] Environment=reason=BOUND ExecStart=/bin/sh -c '. /etc/dhcp/dhclient-exit-hooks.d/ntpsec'
