Your message dated Mon, 05 Oct 2009 16:17:31 +0000
with message-id <e1muqff-0004xu...@ries.debian.org>
and subject line Bug#549571: fixed in corosync 1.0.0-7
has caused the Debian Bug report #549571,
regarding corosync: Incorrect init.d script dependencies
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.)
--
549571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: corosync
Version: 1.0.0-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 scripts of this package. The scripts uses files
in /usr/ and should depend on $remote_fs.
Btw, as the script start a daemon, it should not really start in
rcS.d/, but instead start in runlevels 2-5, to get switching to and
from runlevel 1 working properly. This will require more changes than
this patch provides.
This patch should solve the dependency issue. Setting severity to
serious, the script will start to early during boot.
diff -ur ../corosync-1.0.0/debian/corosync.init
../corosync-1.0.0-pere/debian/corosync.init
--- ../corosync-1.0.0/debian/corosync.init 2009-10-04 15:19:37.000000000
+0200
+++ ../corosync-1.0.0-pere/debian/corosync.init 2009-10-04 15:20:38.000000000
+0200
@@ -2,10 +2,8 @@
#
### BEGIN INIT INFO
# Provides: corosync
-# Required-Start: $network
-# Required-Stop: $network
-# Should-Start:
-# Should-Stop:
+# Required-Start: $network $remote_fs
+# Required-Stop: $network $remote_fs
# Default-Start: S
# Default-Stop: 0 1 6
# Short-Description: corosync cluster framework
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: corosync
Source-Version: 1.0.0-7
We believe that the bug you reported is fixed in the latest version of
corosync, which is due to be installed in the Debian FTP archive:
corosync-dbg_1.0.0-7_i386.deb
to pool/main/c/corosync/corosync-dbg_1.0.0-7_i386.deb
corosync_1.0.0-7.diff.gz
to pool/main/c/corosync/corosync_1.0.0-7.diff.gz
corosync_1.0.0-7.dsc
to pool/main/c/corosync/corosync_1.0.0-7.dsc
corosync_1.0.0-7_i386.deb
to pool/main/c/corosync/corosync_1.0.0-7_i386.deb
libcorosync-dev_1.0.0-7_i386.deb
to pool/main/c/corosync/libcorosync-dev_1.0.0-7_i386.deb
libcorosync4_1.0.0-7_i386.deb
to pool/main/c/corosync/libcorosync4_1.0.0-7_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 549...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guido Günther <a...@sigxcpu.org> (supplier of updated corosync 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, 05 Oct 2009 17:54:22 +0200
Source: corosync
Binary: corosync corosync-dbg libcorosync4 libcorosync-dev
Architecture: source i386
Version: 1.0.0-7
Distribution: unstable
Urgency: low
Maintainer: Debian HA Maintainers
<debian-ha-maintain...@lists.alioth.debian.org>
Changed-By: Guido Günther <a...@sigxcpu.org>
Description:
corosync - Standards-based cluster framework (daemon and modules)
corosync-dbg - Standards-based cluster framework (debugging symbols)
libcorosync-dev - Standards-based cluster framework (developer files)
libcorosync4 - Standards-based cluster framework (libraries)
Closes: 549571 549634 549636
Changes:
corosync (1.0.0-7) unstable; urgency=low
.
* [a300993] Conflict on openais (Closes: #549634)
* [00d0531] Conflict openais-legacy-dev (Closes: #549636)
* [64f4fa2] Add missing init script dependency on $remote_fs since we use
files in /usr/. (Closes: #549571) - thanks to Petter Reinholdtsen
Checksums-Sha1:
067c1b6be6020a5f1d7ab0b01d1a95294d5462e6 1289 corosync_1.0.0-7.dsc
18f7202849dc265186bf9745524180296ee2c556 11212 corosync_1.0.0-7.diff.gz
e49beef97010a9ec4c4d87398524e68b5e4de814 342892 corosync_1.0.0-7_i386.deb
00c475fc2c9d598c30d984efd0739f88f77325a4 2114234 corosync-dbg_1.0.0-7_i386.deb
d1f92e03474c77750e4ee7aed12022dd3afeb1a2 252984 libcorosync4_1.0.0-7_i386.deb
4ba3766a88551860c01ab3d2020817fce6ed4864 374400
libcorosync-dev_1.0.0-7_i386.deb
Checksums-Sha256:
7a817d99b9c20e6a750c2870a2eb51b37387cfa4b37723e1a5f93022809a13f7 1289
corosync_1.0.0-7.dsc
f0d7fe95004d0977c1962ee713f2818264cc3eafa54e011aa0fef0951d3f0da6 11212
corosync_1.0.0-7.diff.gz
17bdc026ff6d0a5e05d5a77c0b0dda67ddc0ae578edc0644c8e4e6011c224d6d 342892
corosync_1.0.0-7_i386.deb
6ee6a84bfae0366e1453c2d818d00a71f24a2e20b803e32291da5ba17d19c64e 2114234
corosync-dbg_1.0.0-7_i386.deb
1141891480ffd33992fcdfa55382b3abe81544068bb5725e1eeccf61ad8bc9ed 252984
libcorosync4_1.0.0-7_i386.deb
9ab14294269c40712bde93a27a4bb1024e66ac29a2ad9469892a722427fc0e85 374400
libcorosync-dev_1.0.0-7_i386.deb
Files:
be6d6983bce2c3680ff913d9d80bc5c2 1289 admin optional corosync_1.0.0-7.dsc
cb973f255b8d52ea3fe0695ce7a9520a 11212 admin optional corosync_1.0.0-7.diff.gz
2e5e9b456e0a80d48cf0337c1bbcb6b7 342892 admin optional
corosync_1.0.0-7_i386.deb
4a2ffd837ece8546b7ec3df1f4c32a16 2114234 debug extra
corosync-dbg_1.0.0-7_i386.deb
e1166a65834ca06d9e67b7d075a00800 252984 libs optional
libcorosync4_1.0.0-7_i386.deb
f0edf9ccc369df9df5bd440d46fdfe4d 374400 libdevel optional
libcorosync-dev_1.0.0-7_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFKyhf/n88szT8+ZCYRAvqTAJ4ipvA+htClOcewBKDL1coTuhaRXwCeNAsG
TzrAjeHcNCEF8j9lVXetlME=
=dlFe
-----END PGP SIGNATURE-----
--- End Message ---
