Greetings, I'm packaging up a firewall script that ships with a systemd service unit file. lintian is complaining about an init script:
% lintian fw-skel_0.06-1_all.deb 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 % There is, of course, no init script: % dpkg-deb -c fw-skel_0.06-1_all.deb | grep init % The postinst and prerm both reference an absent init script: % dpkg-deb -e fw-skel_0.06-1_all.deb % grep init DEBIAN/* DEBIAN/postinst:# Automatically added by dh_installinit DEBIAN/postinst:if [ -x "/etc/init.d/fw-skel" ]; then DEBIAN/postrm:# Automatically added by dh_installinit DEBIAN/prerm:# Automatically added by dh_installinit DEBIAN/prerm:if [ -x "/etc/init.d/fw-skel" ]; then % It seems that dh-systemd is working in some capacity: % dpkg-deb -c fw-skel_0.06-1_all.deb| grep systemd drwxr-xr-x root/root 0 2015-09-23 15:18 ./lib/systemd/ drwxr-xr-x root/root 0 2015-09-23 15:18 ./lib/systemd/system/ -rw-r--r-- root/root 200 2015-09-23 15:18 ./lib/systemd/system/fw-skel.service % I'm building this using a sid cowbuilder + gbp, FWIW. Any ideas for keeping SysV init out of the postinst and friends? Thanks! -m