[Pkg-sysvinit-commits] r1713 - sysvinit/trunk/debian

[Petter Reinholdtsen]

Author: pere
Date: 2009-09-04 19:34:25 +0000 (Fri, 04 Sep 2009)
New Revision: 1713

Modified:
   sysvinit/trunk/debian/sysv-rc.templates
Log:
Try to improve langauge even more.

Modified: sysvinit/trunk/debian/sysv-rc.templates
===================================================================
--- sysvinit/trunk/debian/sysv-rc.templates	2009-09-04 19:10:29 UTC (rev 1712)
+++ sysvinit/trunk/debian/sysv-rc.templates	2009-09-04 19:34:25 UTC (rev 1713)
@@ -26,8 +26,8 @@
  .
  This migration process is non-reversible. The legacy way of ordering
  boot scripts using static sequence numbers will be made obsolete by
- choosing to migrate.  Any boot sequence changes done manually will
- have to redone using dependencies.
+ choosing to migrate.  Any boot sequence changes done locally will be
+ lost and have to redone using dependencies.
  .
  See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for
  more information about dependency based boot sequencing. To
@@ -48,11 +48,12 @@
     by preserving the boot sequence when problems are detected; the boot
     sequence is only modified if it is safe to do so
  .
- The detected problems need to be reported to and fixed manually or by the
- maintainer of the package/software which installed a problematic boot init.d
- script. See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for
- more information about how to fix the problems preventing migration. To
- reattempt the migration process after the problems have been fixed, run
- 'dpkg-reconfigure sysv-rc'.
+ If the reported problem is a local modification it needs to be fixed
+ manually.  If it's a bug in the package it should be reported to the
+ BTS and fixed in the package. See
+ http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for more
+ information about how to fix the problems preventing migration. To
+ reattempt the migration process after the problems have been fixed,
+ run 'dpkg-reconfigure sysv-rc'.
  .
  The following problems were detected: ${PROBLEMATIC}