Bug#534326: wrong lintian messages on a package using (provisional) dh_installupstart
While implementing a dh_installupstart command that installs upstart jobs
for packages and provides compatibility symlinks in /etc/init.d for a
wrapper, lintian spit out the following messages on my test package:
W: cups: init.d-script-not-marked-as-conffile /etc/init.d/cups
N: /etc/init.d scripts should be marked as conffiles.
N: This is usually an error, but the Policy allows for managing these files
N: manually in maintainer scripts and Lintian cannot reliably detect that.
N: Refer to Debian Policy Manual section 9.3.2 (Writing the scripts) for
N: Severity: important, Certainty: wild-guess
E: cups: init.d-script-not-included-in-package /etc/init.d/cups
N: The /etc/init.d script is registered in the postinst script, but is not
N: included in the package.
N: Severity: important, Certainty: certain
The first lintian check should know to exclude symlinks. The second one
should probably do the same, or at least check the validity of the target
against some sort of relevant whitelist (in this case: packages depending on
virtual package 'upstart-job' and linking to '/lib/init/upstart-job' are
The combination of the two lintian messages on a single package is amusing.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/