Package: debhelper
Version: 13.2.1
Severity: normal
I'm working on a modification for mlocate to add a systemd unit file[1]
that is intended to be activated by systemd timer, so, not run as a
daemon, and not analoguous to an init script. The unit is not installed
(has no [Install] section) and the package does not ship an init script.
(There's a .timer unit, too, which does have an [Install] section.)
The presence of the .service file, though, causes dh_installinit to
generate postinst snippets like this
# Automatically added by dh_installinit/13.2.1
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [
"$1" = "abort-remove" ] ; then
if [ -x "/etc/init.d/mlocate" ]; then
update-rc.d mlocate defaults >/dev/null
This is superfluous, but relatively benign because it's guarded by
"[ -x". However, it triggers a Lintian test of severity "error".
E: mlocate: init.d-script-not-included-in-package etc/init.d/mlocate
N:
N: The /etc/init.d script is registered in the postinst script, but is
N: not included in the package.
N:
N: Severity: error
N:
N: Check: init.d
I've hesitated over whether to file this against debhelper, or the lintian
test, but the lintian test is "right", so far as it goes: the postinst does
reference an init script that is not included in the package. One could argue
the severity/certainty is wrong given the guard, I suppose. I'm CCing the
Lintian maintainers for their info.
[1]
https://salsa.debian.org/debian/mlocate/-/commit/5df4fd837132cfbe1673977033c78a0b829e9bd1
but it's still a work-in-progress
Best wishes,
--
👱🏻 Jonathan Dowland
✎ j...@debian.org
🔗 https://jmtd.net
