Your message dated Thu, 17 Sep 2009 22:47:37 +0000
with message-id <e1moplj-0001ui...@ries.debian.org>
and subject line Bug#546502: fixed in cryptmount 4.0.1-1
has caused the Debian Bug report #546502,
regarding cryptmount: Incorrect dependencies in init.d script
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
546502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptmount
Version: 1.1-2
Severity: serious
Tags: patch
User: initscripts-ng-de...@lists.alioth.debian.org
Usertags: incorrect-dependency
With dependency based boot sequencing, I discovered what I believe is
a bug in the init.d script. The scripts uses files in /usr/, but do
not depend on $remote_fs. Also, the cryptmount-early script starts in
rcS.d but depend on $syslog. This is an impossible dependency, as the
syslog collector is started in runlevels 2-5 after rcS.d/ is complete.
Finally, I suspect the cryptmount script expect the cryptmount-early
script to run before it, and this relationship should be explicitly
stated to make sure concurrent booting work as expected.
<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 >.
This patch should fix the issues. Setting severity serious as the
script will fail to work if /usr/ is on a separate partition, not yet
mounted when the scripts are executed too early during boot.
diff -ur cryptmount-4.0/initscript-early.in
cryptmount-4.0-pere/initscript-early.in
--- cryptmount-4.0/initscript-early.in 2009-05-04 08:07:28.000000000 +0200
+++ cryptmount-4.0-pere/initscript-early.in 2009-09-13 19:51:43.000000000
+0200
@@ -6,10 +6,8 @@
# Basic support for Linux Standard Base:
### BEGIN INIT INFO
# Provides: cryptmount-early
-# Required-Start: $syslog
-# Required-Stop: $syslog
-# Should-Start: $local_fs
-# Should-Stop: $local_fs
+# Required-Start: $remote_fs
+# Required-Stop: $remote_fs
# Default-Start: S
# Default-Stop: 0 6
# Short-Description: setup encrypted devices at boot
diff -ur cryptmount-4.0/initscript.in cryptmount-4.0-pere/initscript.in
--- cryptmount-4.0/initscript.in 2009-05-04 08:07:28.000000000 +0200
+++ cryptmount-4.0-pere/initscript.in 2009-09-13 19:53:57.000000000 +0200
@@ -6,10 +6,8 @@
# Basic support for Linux Standard Base:
### BEGIN INIT INFO
# Provides: cryptmount
-# Required-Start: $syslog
-# Required-Stop: $syslog
-# Should-Start: $local_fs
-# Should-Stop: $local_fs
+# Required-Start: $remote_fs $syslog cryptmount-early
+# Required-Stop: $remote_fs $syslog cryptmount-early
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: setup encrypted filesystems/swap at boot
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: cryptmount
Source-Version: 4.0.1-1
We believe that the bug you reported is fixed in the latest version of
cryptmount, which is due to be installed in the Debian FTP archive:
cryptmount_4.0.1-1.diff.gz
to pool/main/c/cryptmount/cryptmount_4.0.1-1.diff.gz
cryptmount_4.0.1-1.dsc
to pool/main/c/cryptmount/cryptmount_4.0.1-1.dsc
cryptmount_4.0.1-1_amd64.deb
to pool/main/c/cryptmount/cryptmount_4.0.1-1_amd64.deb
cryptmount_4.0.1.orig.tar.gz
to pool/main/c/cryptmount/cryptmount_4.0.1.orig.tar.gz
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 546...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
RW Penney <rwpen...@users.sourceforge.net> (supplier of updated cryptmount
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 ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Mon, 14 Sep 2009 20:00:00 +0000
Source: cryptmount
Binary: cryptmount
Architecture: source amd64
Version: 4.0.1-1
Distribution: unstable
Urgency: low
Maintainer: RW Penney <rwpen...@users.sourceforge.net>
Changed-By: RW Penney <rwpen...@users.sourceforge.net>
Description:
cryptmount - Management of encrypted file systems
Closes: 546502
Changes:
cryptmount (4.0.1-1) unstable; urgency=low
.
* Updated to version 4.0.1 of upstream package
.
* Closes: bug#546502 (Incorrect dependencies in /etc/init.d scripts)
Checksums-Sha1:
5565b16ace9689d48a3209587f0817d22e5924b8 1095 cryptmount_4.0.1-1.dsc
2e533a44db5a87c560da32c7f83f701b194472f2 386181 cryptmount_4.0.1.orig.tar.gz
882a157bca8ef111acaf4f77b549e82d0c2c624d 17290 cryptmount_4.0.1-1.diff.gz
2f1d3d6cbf45054ec34accfdaedb8dc7bc38d726 123206 cryptmount_4.0.1-1_amd64.deb
Checksums-Sha256:
bfca9a348268b26b7b3ba4363ee4982f6f5f3f075362bb10524212590a8da3b1 1095
cryptmount_4.0.1-1.dsc
2e1ed2ec9f9f1c88fd9d39090e19f666f662dfb61ed6b98dc8b0fdfc6b9b26a5 386181
cryptmount_4.0.1.orig.tar.gz
e8a3c32451b6d87f77d464180782baaa7c32d117c5cc26bb4542c4db23201654 17290
cryptmount_4.0.1-1.diff.gz
fae23cd997137825f96b992e7721ffe234a33496a1ba8aa498e3f650b60dc081 123206
cryptmount_4.0.1-1_amd64.deb
Files:
7f2b9bc634adce7dbe572cd8ede217c7 1095 admin extra cryptmount_4.0.1-1.dsc
cb7affd044976e8a04c69b9ef91f4e6d 386181 admin extra
cryptmount_4.0.1.orig.tar.gz
ac50151765fb724cc815eb924ccdd7fc 17290 admin extra cryptmount_4.0.1-1.diff.gz
ff5f205c0ef0512881ba4328fd724a76 123206 admin extra
cryptmount_4.0.1-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkqyuHQACgkQMDatjqUaT902qQCeN1MGI7f7VGLy/OvXgIbe598e
h4YAoKutPC4scXm027ZZu/EJKD4u90JO
=ILJ3
-----END PGP SIGNATURE-----
--- End Message ---
