I have uploaded the package now but I received a lintian warning during dput (see below). I mistakenly only ran lintian on the source package before the upload...
I suppose fixing this is as easy as replacing # Provides: shishid with # Provides: shishi-kdc in /etc/init.d/shishi-kdc but I'm not sure about backwards compatibility. What if some service depends on the "shishid" service (not likely but maybe possible?). Is this possible: # Provides: shishi-kdc shishid Even if it is possible, and we'd use it, I wonder when it would be safe to remove the 'shishid' part. Keeping 'shishid' in the Provides: may result in people starting to use it. So maybe it is simpler to just change 'shishid' to 'shishi-kdc' and deal with any breakage separately now rather than later. I don't think there is any service that would depend on the 'shishid' service being started? /Simon j...@mocca:~/src/shishi-0.0.40$ lintian --pedantic -E -I -i /var/cache/pbuilder/result/shishi_0.0.40-2.dsc j...@mocca:~/src/shishi-0.0.40$ j...@mocca:/var/cache/pbuilder/result$ dput -l ftp-master shishi_0.0.40-2_i386.changes Checking signature on .changes gpg: Signature made Wed 07 Oct 2009 10:18:33 AM CEST using RSA key ID B565716F gpg: Good signature from "Simon Josefsson <si...@josefsson.org>" gpg: aka "Simon Josefsson <j...@extundo.com>" Good signature on /var/cache/pbuilder/result/shishi_0.0.40-2_i386.changes. Checking signature on .dsc gpg: Signature made Wed 07 Oct 2009 10:18:30 AM CEST using RSA key ID B565716F gpg: Good signature from "Simon Josefsson <si...@josefsson.org>" gpg: aka "Simon Josefsson <j...@extundo.com>" Good signature on /var/cache/pbuilder/result/shishi_0.0.40-2.dsc. Package is now being checked with lintian. W: shishi-kdc: init.d-script-does-not-provide-itself /etc/init.d/shishi-kdc N: N: This /etc/init.d script indicates it provides one or more facilities, N: but none of the provided facilities match the name of the init script. N: In certain cases, it may be necessary to not follow that convention, but N: normally init scripts should always provide a facility matching the name N: of the init script. N: N: Refer to http://wiki.debian.org/LSBInitScripts for details. N: N: Severity: normal, Certainty: possible N: dput -l ftp-master shishi_0.0.40-2_i386.changes Uploading to ftp-master (via ftp to ftp.upload.debian.org): Uploading shishi_0.0.40-2.dsc: done. Uploading shishi_0.0.40-2.diff.gz: done. Uploading shishi-common_0.0.40-2_all.deb: done. Uploading shishi-doc_0.0.40-2_all.deb: done. Uploading libshishi0_0.0.40-2_i386.deb: done. Uploading libshisa0_0.0.40-2_i386.deb: done. Uploading shishi_0.0.40-2_i386.deb: done. Uploading shishi-dbg_0.0.40-2_i386.deb: done. Uploading libshishi-dev_0.0.40-2_i386.deb: done. Uploading shisa_0.0.40-2_i386.deb: done. Uploading libshisa-dev_0.0.40-2_i386.deb: done. Uploading shishi-kdc_0.0.40-2_i386.deb: done. Uploading libpam-shishi_0.0.40-2_i386.deb: done. Uploading shishi_0.0.40-2_i386.changes: done. Successfully uploaded packages. j...@mocca:/var/cache/pbuilder/result$ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
