Bug#469995: marked as done (xdm: Problem with LSB header in init.d script)
Your message dated Wed, 12 Mar 2008 14:17:09 +0000
with message-id <E1JZRlV-0007C3-Aa@ries.debian.org>
and subject line Bug#469995: fixed in xdm 1:1.1.7-1
has caused the Debian Bug report #469995,
regarding xdm: Problem with LSB header 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 owner@bugs.debian.org
immediately.)
--
469995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469995
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xdm
Version: 1:1.1.4-1
Severity: important
Tags: patch
User: initscripts-ng-devel@lists.alioth.debian.org
Usertags: incorrect-dependency
I just checked the shutdown order in unstable on a machine with
dependency based boot sequencing enabled, and discovered that the xdm
got a stop symlink in rcS.d/. This is wrong and only slow down the
boot (very slightly, but still unwanted. :).
Here is a patch to solve it.
diff -ur xdm-1.1.6.orig/debian/xdm.init xdm-1.1.6/debian/xdm.init
--- xdm-1.1.6.orig/debian/xdm.init 2008-03-08 16:51:04.000000000 +0100
+++ xdm-1.1.6/debian/xdm.init 2008-03-08 16:51:51.000000000 +0100
@@ -27,7 +27,7 @@
# Should-Start: xfs $named slapd
# Should-Stop: xfs $named slapd
# Default-Start: 2 3 4 5
-# Default-Stop: S 0 1 6
+# Default-Stop: 0 1 6
### END INIT INFO
set -e
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: xdm
Source-Version: 1:1.1.7-1
We believe that the bug you reported is fixed in the latest version of
xdm, which is due to be installed in the Debian FTP archive:
xdm_1.1.7-1.diff.gz
to pool/main/x/xdm/xdm_1.1.7-1.diff.gz
xdm_1.1.7-1.dsc
to pool/main/x/xdm/xdm_1.1.7-1.dsc
xdm_1.1.7-1_i386.deb
to pool/main/x/xdm/xdm_1.1.7-1_i386.deb
xdm_1.1.7.orig.tar.gz
to pool/main/x/xdm/xdm_1.1.7.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 469995@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Julien Cristau <jcristau@debian.org> (supplier of updated xdm 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: Wed, 12 Mar 2008 15:02:54 +0100
Source: xdm
Binary: xdm
Architecture: source i386
Version: 1:1.1.7-1
Distribution: unstable
Urgency: low
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Julien Cristau <jcristau@debian.org>
Description:
xdm - X display manager
Closes: 468553 469995
Changes:
xdm (1:1.1.7-1) unstable; urgency=low
.
[ David Nusinow ]
* Add Finnish translation, courtesy of Esko Arajärvi. closes: #468553
.
[ Julien Cristau ]
* New upstream release.
* Refresh patches.
* Fix LSB header in xdm.init: don't stop in the S runlevel. Thanks, Petter
Reinholdtsen (closes: #469995).
.
[ Brice Goglin ]
* Add the upstream URL to debian/copyright.
* Add Vcs-Git and Vcs-Browser fields.
* Bump Standards-Version: to 3.7.3, no change needed.
Files:
e69fd6c9a1c7068e525eb85127ac7a03 1007 x11 optional xdm_1.1.7-1.dsc
74ca22dfc7763170761872d0737d6f21 529060 x11 optional xdm_1.1.7.orig.tar.gz
d806dd1d0a233524e155c71b8d3297d1 105352 x11 optional xdm_1.1.7-1.diff.gz
7ee6aa2f885e7f0a93795b02ef9ca580 189810 x11 optional xdm_1.1.7-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH1+TWmEvTgKxfcAwRAoSvAJ9yMMhw/6fYfZuqng+vqnq4c+twoQCgvuv1
yEAUtKbFavdwG4gnPuxC1Vs=
=rh9c
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: