[debhelper-devel] Bug#800043: dh-systemd: add documentation for using dh-systemd
niels at thykier.net
Mon Apr 10 09:50:00 UTC 2017
Control: tags -1 -moreinfo +pending
> On Fri, Apr 7, 2017 at 8:31 AM, Niels Thykier <niels at thykier.net> wrote:
>> What is your view? Are you still missing something from the
>> documentation on the systemd helpers?
> When using tiny rules:
> dh $@
> and the package contains a systemd unit file, but no sysv init file,
> lintian complains:
> W: fw-skel: init.d-script-not-marked-as-conffile etc/init.d/fw-skel
> E: fw-skel: init.d-script-not-included-in-package etc/init.d/fw-skel
Aha. I believe that is fixed in compat 11 (still WIP though). In
compat 11, dh_installinit will ignore systemd files and accordingly not
assume it should do something.
> I don't know the best place to document this idea of telling debhelper to
> not bother with the init script if it doesn't exist.
I have added a remark in the dh_installinit manpage about it might make
sense to skip dh_installinit for packages in compat 10 and earlier, when
they only skip systemd services and no sysvinit scripts.
The actual text being (review welcome):
In compat 10 or earlier: If a package only ships a systemd service
file and no sysvinit script is provided, you may want to exclude the
call to dh_installinit for that package (e.g. via B<-N>). Otherwise,
you may get warnings from lintian about init.d scripts not being
included in the package.
> Perhaps I should file a bug against debhelper.
You already did. ;) When dh-systemd was merged into debhelper, all of
its outstanding bugs got reassigned to debhelper.
More information about the debhelper-devel