[Marco d'Itri]
> I explained many times that no package but the inetds should depend
> on update-inetd. Please fix.

Have not seen any of your explanations, but assume your claim is
correct.  Note that lintian report this:

W: binkd: maintainer-script-needs-depends-on-update-inetd postinst
W: binkd: maintainer-script-needs-depends-on-update-inetd prerm

I leave for you to fix that the way you want it fixed. :)

Here is the new NMU patch, only solving the month old repurt about
missing LSB header in the init.d script.

diff -u binkd-0.9.9+20060809/debian/changelog 
binkd-0.9.9+20060809/debian/changelog
--- binkd-0.9.9+20060809/debian/changelog
+++ binkd-0.9.9+20060809/debian/changelog
@@ -1,3 +1,20 @@
+binkd (0.9.9+20060809-1.2) unstable; urgency=low
+
+  * Followup Non-maintainer upload to solve release goal.
+  * Drop patch to include update-inetd, as the maintainer
+    do not want it.  See #469268 for info.
+
+ -- Petter Reinholdtsen <[EMAIL PROTECTED]>  Fri,  4 Apr 2008 22:08:04 +0200
+
+binkd (0.9.9+20060809-1.1) unstable; urgency=low
+
+  * Non-maintainer upload to solve release goal.
+  * Add LSB dependency header to init.d scripts (Closes: #469268).
+  * Add update-inetd as dependency.  Based on patch from Lionel
+    Porcheron and Ubuntu.
+
+ -- Petter Reinholdtsen <[EMAIL PROTECTED]>  Fri,  4 Apr 2008 19:38:16 +0200
+
 binkd (0.9.9+20060809-1) unstable; urgency=medium

   * New upstream snapshot.
diff -u binkd-0.9.9+20060809/debian/binkd.init 
binkd-0.9.9+20060809/debian/binkd.init
--- binkd-0.9.9+20060809/debian/binkd.init
+++ binkd-0.9.9+20060809/debian/binkd.init
@@ -1,4 +1,11 @@
 #!/bin/sh -e
+### BEGIN INIT INFO
+# Provides:          binkd
+# Required-Start:    $remote_fs $syslog
+# Required-Stop:     $remote_fs $syslog
+# Default-Start:     2 3 4 5
+# Default-Stop:      0 1 6
+### END INIT INFO

 OPTS="/etc/binkd/binkd.cfg -q"
 PIDFILE=/var/run/ftn/binkd.pid

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to