This is the patch I used in the NMU I just uploaded to solve this issue. Note that the provides header was adjusted to match the installed script name.
diff -u scsitools-0.10/debian/changelog scsitools-0.10/debian/changelog --- scsitools-0.10/debian/changelog +++ scsitools-0.10/debian/changelog @@ -1,3 +1,10 @@ +scsitools (0.10-1.1) unstable; urgency=low + + * Non-maintainer upload to solve release goal issues. + * Add LSB dependency header to init.d scripts (Closes: #458649) + + -- Petter Reinholdtsen <[EMAIL PROTECTED]> Sat, 15 Mar 2008 10:53:29 +0100 + scsitools (0.10-1) unstable; urgency=low * Updated scsidev to 2.37 which supports sysfs filenames from linux kernel diff -u scsitools-0.10/debian/scsitools-pre.sh scsitools-0.10/debian/scsitools-pre.sh --- scsitools-0.10/debian/scsitools-pre.sh +++ scsitools-0.10/debian/scsitools-pre.sh @@ -1,6 +1,13 @@ #!/bin/sh -# -# scsitools-pre.sh Create aliases for SCSI devices under /dev/scsi +### BEGIN INIT INFO +# Provides: scsitools-pre +# Required-Start: mountdevsubfs +# Required-Stop: +# X-Start-Before: checkroot +# Default-Start: S +# Default-Stop: +# Short-Description: Create aliases for SCSI devices under /dev/scsi +### END INIT INFO # # This script is run early at boot time (before S10checkroot.sh), so / is not # yet writable. Therefore it is needed to set up a ramdisk for /dev/scsi. diff -u scsitools-0.10/debian/scsitools.sh scsitools-0.10/debian/scsitools.sh --- scsitools-0.10/debian/scsitools.sh +++ scsitools-0.10/debian/scsitools.sh @@ -1,6 +1,13 @@ #!/bin/sh -# -# scsitools.sh Create aliases for SCSI devices under /dev/scsi +### BEGIN INIT INFO +# Provides: scsitools +# Required-Start: checkroot +# Required-Stop: +# X-Start-Before: checkfs +# Default-Start: S +# Default-Stop: +# Short-Description: Create aliases for SCSI devices under /dev/scsi +### END INIT INFO # # This is the second part of populating /dev/scsi. Now / is writable, so # remove the ramdisk and recreate the tree. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
