Debian Bug report logs - #458626
dmraid: Please add LSB formatted dependency info in init.d script

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Petter Reinholdtsen <pere@hungry.com>

To: submit@bugs.debian.org

Subject: dmraid: Please add LSB formatted dependency info in init.d script

Date: Wed, 02 Jan 2008 09:56:57 +0100

Package:  dmraid
Version:  1.0.0.rc13-1
Tags:     patch
User:     initscripts-ng-devel@lists.alioth.debian.org
Usertags: missing-dependency

To be able to check boot script order, and also to be able to start
boot scripts in parallel, it is important to know the dependencies of
the various boot scripts.  The Linux Software Base specifies a init.d
header file format useful for this purpose, and adding such header to
the init.d script would make it possible for me to use this
information to check the current sequence and to speed up the debian
boot.

I am working on a system to update the boot sequence based on these
dependencies, and would like see this as the default in Lenny.
Because of this, it is nice if the dependencies was updated quickly.

<URL:http://refspecs.freestandards.org/LSB_2.1.0/LSB-generic/LSB-generic/initscrcomconv.html>
documents the LSB header format.  Some debian notes are available from
<URL:http://wiki.debian.org/LSBInitScripts>.

Here is a patch to document the dependencies.  I hope this is correct.

diff -ur dmraid-1.0.0.rc13.orig/debian/dmraid.init dmraid-1.0.0.rc13/debian/dmraid.init
--- dmraid-1.0.0.rc13.orig/debian/dmraid.init   2008-01-02 09:48:14.000000000 +0100
+++ dmraid-1.0.0.rc13/debian/dmraid.init        2008-01-02 09:53:07.000000000 +0100
@@ -1,4 +1,13 @@
 #!/bin/bash
+### BEGIN INIT INFO
+# Provides:          dmraid
+# Required-Start:    mountkernfs udev
+# Required-Stop:     umountroot
+# X-Start-Before:    checkroot mdadm-raid lvm
+# X-Stop-After:      umountfs mdadm-raid lvm
+# Default-Start:     S
+# Default-Stop:      0 6
+### END INIT INFO

 # try to load module in case that hasn't been done yet
 modprobe dm-mod >/dev/null 2>&1

Happy hacking,
--
Petter Reinholdtsen

Message #10 received at 458626@bugs.debian.org (full text, mbox, reply):

From: Petter Reinholdtsen <pere@hungry.com>

To: 458626@bugs.debian.org

Subject: Patch used in NMU

Date: Tue, 18 Mar 2008 18:09:42 +0100

This is the patch I used in the NMU to solve this issue.

diff -u dmraid-1.0.0.rc13/debian/changelog dmraid-1.0.0.rc13/debian/changelog
--- dmraid-1.0.0.rc13/debian/changelog
+++ dmraid-1.0.0.rc13/debian/changelog
@@ -1,3 +1,10 @@
+dmraid (1.0.0.rc13-2.1) unstable; urgency=low
+
+  * Non-maintainer upload to solve release goal.
+  * Add LSB dependency header to init.d scripts (Closes: #458626)
+
+ -- Petter Reinholdtsen <pere@debian.org>  Tue, 18 Mar 2008 17:57:38 +0100
+
 dmraid (1.0.0.rc13-2) unstable; urgency=high

   * Apply patch to link libz statically, but only that; works only with GNU
diff -u dmraid-1.0.0.rc13/debian/dmraid.init dmraid-1.0.0.rc13/debian/dmraid.init
--- dmraid-1.0.0.rc13/debian/dmraid.init
+++ dmraid-1.0.0.rc13/debian/dmraid.init
@@ -1,4 +1,13 @@
 #!/bin/bash
+### BEGIN INIT INFO
+# Provides:          dmraid
+# Required-Start:    mountkernfs udev
+# Required-Stop:     umountroot
+# X-Start-Before:    checkroot mdadm-raid lvm2 lvm
+# X-Stop-After:      umountfs  mdadm-raid lvm2 lvm
+# Default-Start:     S
+# Default-Stop:      0 6
+### END INIT INFO

 # try to load module in case that hasn't been done yet
 modprobe dm-mod >/dev/null 2>&1

Message #15 received at 458626-close@bugs.debian.org (full text, mbox, reply):

From: Petter Reinholdtsen <pere@debian.org>

To: 458626-close@bugs.debian.org

Subject: Bug#458626: fixed in dmraid 1.0.0.rc13-2.1

Date: Tue, 18 Mar 2008 17:17:05 +0000

Source: dmraid
Source-Version: 1.0.0.rc13-2.1

We believe that the bug you reported is fixed in the latest version of
dmraid, which is due to be installed in the Debian FTP archive:

dmraid-udeb_1.0.0.rc13-2.1_i386.udeb
  to pool/main/d/dmraid/dmraid-udeb_1.0.0.rc13-2.1_i386.udeb
dmraid_1.0.0.rc13-2.1.diff.gz
  to pool/main/d/dmraid/dmraid_1.0.0.rc13-2.1.diff.gz
dmraid_1.0.0.rc13-2.1.dsc
  to pool/main/d/dmraid/dmraid_1.0.0.rc13-2.1.dsc
dmraid_1.0.0.rc13-2.1_i386.deb
  to pool/main/d/dmraid/dmraid_1.0.0.rc13-2.1_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 458626@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Petter Reinholdtsen <pere@debian.org> (supplier of updated dmraid package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 18 Mar 2008 17:57:38 +0100
Source: dmraid
Binary: dmraid dmraid-udeb
Architecture: source i386
Version: 1.0.0.rc13-2.1
Distribution: unstable
Urgency: low
Maintainer: Utnubu Team <utnubu-maintainers@lists.alioth.debian.org>
Changed-By: Petter Reinholdtsen <pere@debian.org>
Description: 
 dmraid     - Device-Mapper Software RAID support tool
 dmraid-udeb - Device-Mapper Software RAID support tool (udeb)
Closes: 458626
Changes: 
 dmraid (1.0.0.rc13-2.1) unstable; urgency=low
 .
   * Non-maintainer upload to solve release goal.
   * Add LSB dependency header to init.d scripts (Closes: #458626)
Files: 
 0f40f5a09182663daa6e0553b92f555b 787 admin optional dmraid_1.0.0.rc13-2.1.dsc
 d5e3f6525dd6a0e750777e16ca0552c4 4879 admin optional dmraid_1.0.0.rc13-2.1.diff.gz
 ab3368c4ed42740c47930a9f219f10f4 183474 admin optional dmraid_1.0.0.rc13-2.1_i386.deb
 d66e33062ef22b1c5e67f4c52c5d285b 76582 debian-installer optional dmraid-udeb_1.0.0.rc13-2.1_i386.udeb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH3/cT20zMSyow1ykRAlVPAKCW8syxPDsynFZ2O+ytK43rKbBaqwCg091V
1QjSsSDeqFhQ46jc0xjk2qw=
=QLOc
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.