Debian Bug report logs - #538959
insserv/sysv-rc using dependency based boot sequencing break migration to file-rc

Toggle useless messages

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

From: Michael Prokop <mika@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: package fails to remove: error: insserv must be disabled before it is removed, to...

Date: Tue, 28 Jul 2009 10:06:28 +0200

Package: insserv
Version: 1.12.0-10
Severity: important


Fresh and clean sid chroot:

# apt-get install file-rc
Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
  insserv sysv-rc
The following NEW packages will be installed:
  file-rc
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  sysv-rc (due to sysvinit)
0 upgraded, 1 newly installed, 2 to remove and 0 not upgraded.
Need to get 36.6kB of archives.
After this operation, 373kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
 ?] Yes, do as I say!
[...]
error: insserv must be disabled before it is removed, to
error: make sure the boot system is still usable.
error: To disable, run dpkg-reconfigure insserv
dpkg: error processing insserv (--remove):
 subprocess installed pre-removal script returned error exit status 1
[...]

This behaviour didn't exist before insserv 1.12.0-10.

regards,
-mika-

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

From: Alexander Wirt <formorer@formorer.de>

To: 538959@bugs.debian.org

Cc: mika@debian.org, control@bugs.debian.org

Subject: package fails to remove: error: insserv must be disabled before it is removed, to...

Date: Tue, 28 Jul 2009 10:28:26 +0200

severity 538959 critical
thanks

Hi, 

10:16 <formorer> Removing insserv ...
10:16 <formorer> error: insserv must be disabled before it is removed, to
10:16 <formorer> error: make sure the boot system is still usable.
10:16 <formorer> error: To disable, run dpkg-reconfigure insserv
10:16 <formorer> WHOLY FUCK
10:17 <formorer> info: Disabling dependency based boot system
10:17 <formorer> mv: cannot stat `/usr/sbin/update-rc.d.distrib': No such
file or directory
10:17 <formorer> broken, totally broken
10:17 <formorer> I need to reinstall sysv-rc again to disable it

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

From: Petter Reinholdtsen <pere@hungry.com>

To: Alexander Wirt <formorer@formorer.de>, 538959@bugs.debian.org, mika@debian.org

Subject: Re: Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...

Date: Tue, 28 Jul 2009 13:38:04 +0200

[Alexander Wirt]
> severity 538959 critical
> thanks
> 
> Hi, 
> 
> 10:16 <formorer> Removing insserv ...
> 10:16 <formorer> error: insserv must be disabled before it is removed, to
> 10:16 <formorer> error: make sure the boot system is still usable.
> 10:16 <formorer> error: To disable, run dpkg-reconfigure insserv
> 10:16 <formorer> WHOLY FUCK
> 10:17 <formorer> info: Disabling dependency based boot system
> 10:17 <formorer> mv: cannot stat `/usr/sbin/update-rc.d.distrib': No such
> file or directory
> 10:17 <formorer> broken, totally broken
> 10:17 <formorer> I need to reinstall sysv-rc again to disable it

What was leading up to this?  Why did you try to disable insserv?

Insserv will become essential together with sysv-rc, and is not
supposed to be simple to remove any more.  Dependency based boot
sequencing is going to become the default and suppoted boot sequencing
method.  I'll remove the option to disable it.

Happy hacking,
-- 
Petter Reinholdtsen

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

From: Alexander Wirt <formorer@debian.org>

To: Petter Reinholdtsen <pere@hungry.com>

Cc: 538959@bugs.debian.org, mika@debian.org

Subject: Re: Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...

Date: Tue, 28 Jul 2009 13:41:24 +0200

Petter Reinholdtsen schrieb am Tuesday, den 28. July 2009:

> [Alexander Wirt]
> > severity 538959 critical
> > thanks
> > 
> > Hi, 
> > 
> > 10:16 <formorer> Removing insserv ...
> > 10:16 <formorer> error: insserv must be disabled before it is removed, to
> > 10:16 <formorer> error: make sure the boot system is still usable.
> > 10:16 <formorer> error: To disable, run dpkg-reconfigure insserv
> > 10:16 <formorer> WHOLY FUCK
> > 10:17 <formorer> info: Disabling dependency based boot system
> > 10:17 <formorer> mv: cannot stat `/usr/sbin/update-rc.d.distrib': No such
> > file or directory
> > 10:17 <formorer> broken, totally broken
> > 10:17 <formorer> I need to reinstall sysv-rc again to disable it
> 
> What was leading up to this?  Why did you try to disable insserv?
apt-get install file-rc 

> 
> Insserv will become essential together with sysv-rc, and is not
> supposed to be simple to remove any more.  Dependency based boot
> sequencing is going to become the default and suppoted boot sequencing
> method.  I'll remove the option to disable it.
There are other implementations bootmechanisms like file-rc, upstart and so
on. Don't break them!

Really, really not amused about that insserv stuff. 
Alex

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

From: Petter Reinholdtsen <pere@hungry.com>

To: Alexander Wirt <formorer@debian.org>, 538959@bugs.debian.org, mika@debian.org

Subject: Re: Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...

Date: Tue, 28 Jul 2009 13:56:36 +0200

[Alexander Wirt]
>> What was leading up to this?  Why did you try to disable insserv?
> apt-get install file-rc 

Right.  Good to hear that it is the same problem as the initial
report.  May I ask why you are using file-rc?  What advantages does it
have over the current sysv-rc script with concurrent booting?

> There are other implementations bootmechanisms like file-rc, upstart
> and so on. Don't break them!

This problem only affect file-rc.  Upstart is using the sysv-rc
scripts to call the init.d scripts, and insserv work fine with it.

I see two good ways to move forward with this.  One is to convert
file-rc to use dependency based boot sequencing (for example by
rewriting it and insserv to work well together), or drop file-rc from
Debian.

I would really love to work with the file-rc developers to get it to
order the boot sequence using dependency information.

Happy hacking,
-- 
Petter Reinholdtsen

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

From: Alexander Wirt <formorer@debian.org>

To: Petter Reinholdtsen <pere@hungry.com>

Cc: 538959@bugs.debian.org, mika@debian.org

Subject: Re: Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...

Date: Tue, 28 Jul 2009 14:03:36 +0200

Petter Reinholdtsen schrieb am Tuesday, den 28. July 2009:

> [Alexander Wirt]
> >> What was leading up to this?  Why did you try to disable insserv?
> > apt-get install file-rc 
> 
> Right.  Good to hear that it is the same problem as the initial
> report.  May I ask why you are using file-rc?  What advantages does it
> have over the current sysv-rc script with concurrent booting?
It doesn't use insserv. And it is much simpler to administrate for small
systems like laptops or desktops. 

> 
> > There are other implementations bootmechanisms like file-rc, upstart
> > and so on. Don't break them!
> 
> This problem only affect file-rc.  Upstart is using the sysv-rc
> scripts to call the init.d scripts, and insserv work fine with it.
ehm. file-rc uses also the /etc/init.d/ scripts so this answer is not
correct and there are other replacements I didn't mentioned. 

> I see two good ways to move forward with this.  One is to convert
> file-rc to use dependency based boot sequencing (for example by
> rewriting it and insserv to work well together), or drop file-rc from
> Debian.
God no. Insserv is pure crap. Just fix your package its broken like hell. 

Is there any _good_ reason why it has to _depend_ on insserv? (insserv is
fully optional, so there is no need for another essential package). 

> 
> I would really love to work with the file-rc developers to get it to
> order the boot sequence using dependency information.
No, please accept that people don't like this.  

Alex

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

From: Gerfried Fuchs <rhonda@deb.at>

To: Petter Reinholdtsen <pere@hungry.com>, 538959@bugs.debian.org

Subject: Re: Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...

Date: Tue, 28 Jul 2009 14:29:30 +0200

* Petter Reinholdtsen <pere@hungry.com> [2009-07-28 13:38:04 CEST]:
> [Alexander Wirt]
> > Removing insserv ...
> > error: insserv must be disabled before it is removed, to
> > error: make sure the boot system is still usable.
> > error: To disable, run dpkg-reconfigure insserv
> > info: Disabling dependency based boot system
> > mv: cannot stat `/usr/sbin/update-rc.d.distrib': No such file or directory
> 
> What was leading up to this?  Why did you try to disable insserv?

 It doesn't matter why one would want to disable some package. The
package has to be deinstallable fine, no matter how (semi) essential
those packages are. If the package isn't able to get removed properly
(without jumping though hoops) it's broken, it's as simple as that.

> Insserv will become essential together with sysv-rc, and is not
> supposed to be simple to remove any more.

 Please leave that part to the hooks in the package managers that
already have the hoops of requesting users to do something specific to
get it removed anyway - there is no need to add another layer here.

 So long,
Rhonda

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

From: Michael Prokop <mika@debian.org>

To: Petter Reinholdtsen <pere@hungry.com>

Cc: Alexander Wirt <formorer@debian.org>, 538959@bugs.debian.org

Subject: Re: Bug#538959: package fails to remove: error: insserv must be disabled before it is removed, to...

Date: Tue, 28 Jul 2009 14:27:47 +0200

[Message part 1 (text/plain, inline)]

* Petter Reinholdtsen <pere@hungry.com> [20090728 13:56]:
> [Alexander Wirt]
> >> What was leading up to this?  Why did you try to disable insserv?
> > apt-get install file-rc 

> Right.  Good to hear that it is the same problem as the initial
> report.  May I ask why you are using file-rc?  What advantages does it
> have over the current sysv-rc script with concurrent booting?

Speaking for myself why I prefer file-rc: No symlink hell,
copying/distributing just one single file which defines the boot
setup is enough, option to 'grep $service /etc/runlevel.conf', it's
deterministic and just works,...

BTW: How do I know in which order my insserv based system will boot up?

> > There are other implementations bootmechanisms like file-rc, upstart
> > and so on. Don't break them!

> This problem only affect file-rc.  Upstart is using the sysv-rc
> scripts to call the init.d scripts, and insserv work fine with it.

Of course upstart isn't affected because it doesn't conflict with
sysv-rc (which introduced the breakage).

Why should it be such a big deal to fix the package so removing it
works again?

> I see two good ways to move forward with this.  One is to convert
> file-rc to use dependency based boot sequencing (for example by
> rewriting it and insserv to work well together),

OK - but *please* make dependency based booting an option.

> or drop file-rc from Debian.

Please NO.

regards,
-mika-

[signature.asc (application/pgp-signature, inline)]

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

From: Thorsten Glaser <tg@mirbsd.de>

To: 538959@bugs.debian.org

Subject: insserv/sysv-rc using dependency based boot sequencing break migration to file-rc

Date: Sun, 2 Aug 2009 08:38:09 +0000 (UTC)

More reasons:

file-rc is much easier to understand and to get a QUICK overview
of the system boot state and also is more familiar to sysadmins
coming from the BSD world.

Plus, it’s got a lot less overhead.

Please keep supporting file-rc.

//mirabilos
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.		-- Coywolf Qi Hunt

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

From: Petter Reinholdtsen <pere@hungry.com>

To: 538959@bugs.debian.org

Cc: Gerfried Fuchs <rhonda@deb.at>, Michael Prokop <mika@debian.org>, Alexander Wirt <formorer@debian.org>, Thorsten Glaser <tg@mirbsd.de>

Subject: Re: Bug#538959: insserv/sysv-rc using dependency based boot sequencing break migration to file-rc

Date: Sat, 8 Aug 2009 10:36:35 +0200

Those interested in file-rc should check out BTS reports #539591
(convert file-rc to order based on dependency information) and #539609
(reguest for adotion from the file-rc maintainer).  Someone need to
work on file-rc for it to continue as a working solution in Debian.
Mentioning it here in the hope that someone will step up.

The sysv-rc and insserv packages will in the next upload be adjusted
to let another package to take over update-rc.d, but any replacement
need to order scripts the same way - using dependency information.

Happy hacking,
-- 
Petter Reinholdtsen

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

From: Bernd Zeimetz <bzed@debian.org>

To: Petter Reinholdtsen <pere@hungry.com>, 538959@bugs.debian.org

Cc: Gerfried Fuchs <rhonda@deb.at>, Michael Prokop <mika@debian.org>, Alexander Wirt <formorer@debian.org>, Thorsten Glaser <tg@mirbsd.de>

Subject: Re: Bug#538959: insserv/sysv-rc using dependency based boot sequencing break migration to file-rc

Date: Thu, 13 Aug 2009 19:33:22 +0200

Petter Reinholdtsen wrote:
> Those interested in file-rc should check out BTS reports #539591
> (convert file-rc to order based on dependency information) and #539609
> (reguest for adotion from the file-rc maintainer).  Someone need to
> work on file-rc for it to continue as a working solution in Debian.
> Mentioning it here in the hope that someone will step up.
> 
> The sysv-rc and insserv packages will in the next upload be adjusted
> to let another package to take over update-rc.d, but any replacement
> need to order scripts the same way - using dependency information.

*NEED*?
This is utter bullshit. Please point me to a line in policy where we require
that a sysv-rc replacement needs to do a dependency  based boot.This is your
idea, I can't find any place where it was discussed and accepted by the Debian
community. As long as there is no consensus regarding a dependency based boot,
*YOU* have to ensure that the insserv mess does not break people's systems.

-- 
 Bernd Zeimetz                             Debian GNU/Linux Developer
 GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
                   ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F

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

From: Petter Reinholdtsen <pere@debian.org>

To: 538959-close@bugs.debian.org

Subject: Bug#538959: fixed in sysvinit 2.87dsf-3

Date: Sat, 05 Sep 2009 10:53:12 +0000

Source: sysvinit
Source-Version: 2.87dsf-3

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

initscripts_2.87dsf-3_i386.deb
  to pool/main/s/sysvinit/initscripts_2.87dsf-3_i386.deb
sysv-rc_2.87dsf-3_all.deb
  to pool/main/s/sysvinit/sysv-rc_2.87dsf-3_all.deb
sysvinit-utils_2.87dsf-3_i386.deb
  to pool/main/s/sysvinit/sysvinit-utils_2.87dsf-3_i386.deb
sysvinit_2.87dsf-3.diff.gz
  to pool/main/s/sysvinit/sysvinit_2.87dsf-3.diff.gz
sysvinit_2.87dsf-3.dsc
  to pool/main/s/sysvinit/sysvinit_2.87dsf-3.dsc
sysvinit_2.87dsf-3_i386.deb
  to pool/main/s/sysvinit/sysvinit_2.87dsf-3_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 538959@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 sysvinit 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.8
Date: Sat, 05 Sep 2009 11:52:51 +0200
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscripts
Architecture: source i386 all
Version: 2.87dsf-3
Distribution: unstable
Urgency: low
Maintainer: Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>
Changed-By: Petter Reinholdtsen <pere@debian.org>
Description: 
 initscripts - scripts for initializing and shutting down the system
 sysv-rc    - System-V-like runlevel change mechanism
 sysvinit   - System-V-like init utilities
 sysvinit-utils - System-V-like utilities
Closes: 519553 538934 538936 538959 539084 540546 541041 543294 544249 544555 544565
Changes: 
 sysvinit (2.87dsf-3) unstable; urgency=low
 .
   [ Petter Reinholdtsen ]
   * Drop execution of files in /etc/rc.boot from sysv-rc.  This feature
     have been obsolete since before 1999.  Remove the rc.boot(5) manual
     page from the source as well.
   * Make init.d/rc.local depend on $all to get it to start later in
     the boot sequence (Closes: #539084).
   * Rewrite message from update-rc.d to make it more obvious that both
     start and stop symlinks are taken into account (Closes: #519553).
   * Rewrite /etc/rcS.d/README and /etc/rc[2-5].d/README to explain how
     to disable a service at a given runlevel with the dependency based
     boot sequencing.  Remove the list of well known sequence numbers
     in rcS.d/ that is no longer valid with dependency based boot
     sequencing.
   * Make sysv-rc Breaks: initscripts (<< 2.86.ds1-63) to make sure
     scripts working with makefile style concurrent booting is
     installed.  Not using dependency to avoid circular dependency
     between initscripts and sysv-rc.
   * Move the code to migrate to dependency based boot sequencing
     during upgrades from the insserv package to the sysv-rc package.
     Depend on insserv (>> 1.12.0-10) for this.  Let initscripts depend
     on sysv-rc | file-rc to make sure they are installed first.
     Migration is a one-way process, enabled after a critical debconf
     question during upgrades when it is safe to do so (Closes:
     #540546, #541041).  Checks previously done by
     update-bootsystem-insserv are now only done once in sysv-rc
     postinst (Closes: #538934).  Dependency based boot sequencing is
     now the default.  This change make it possible to remove both
     sysv-rc and insserv (Closes: #538959) if other packages want to
     take over the boot sequencing resposibility.
   * Rewrite initscripts postinst to always use the update-rc.d script
     instead of the legacy updatercd() function which was used as a
     speed optimization no longer relevant when dependency based boot
     sequencing is the default.
 .
   [ Kel Modderman ]
   * Migrate from dpatch to quilt for patch management:
     - build-depend on quilt (>= 0.40)
     - provide patch and unpatch targets in debian/rules. use custom
       patch targets to allow for separate debian/patches and
       debian/startpar/patches patch series
     - keep .dpatch file extenstion to make checking changes easier
     - add debian/README.source to describe patch system we use
   * Purge debian/patches/12_doc_lastb.dpatch and
     debian/patches/68_init_quiet.dpatch, they were never applied and wrong.
   * Update patch header for all remaining patches.
   * Call dpkg-shlibdeps debian/startpar/startpar for sysvinit-utils package
     and not sysvinit, startpar moved in revision 2.86.ds1-62.
   * Remove checkdir, checkroot and buildfromsvn targets from
     debian/rules.  The latter is unused by current maintainers and the
     former can be replaced with dh_testdir and dh_testroot instead.
   * Fix reject hunk of debian/patches/70_compiler_warnings.dpatch to
     fix another compile warning.
   * Make sure update-rc.d compares command line parameters for start/stop
     runlevel configuration with the Default-Start and Default-Stop values in
     LSB info comment of script and warns if there are differences.
   * Update sysv-rc debconf templates with text which help explain
     dependency based boot to end users, and provide sound advice for
     people who encounter problems which prevent the migration.
   * Update inittab.kfreebsd-gnu: On GNU/kFreeBSD the serial devices have
     change from /dev/cuuaX to  /dev/ttydX in kernel 6.0 which is minumum
     kernel currently supported in Debian. (Closes: #544555)
   * Make sure sysv-rc/etc/init.d/rc checks insserv has reordered boot
     system by checking for /etc/init.d/.depend.* when CONCURRENCY=shell
     too. (Closes: #544565)
 .
   [ Petter Reinholdtsen ]
   * Adjust init.d/bootlogd dependencies to start before hostname,
     procps, pcmcia, hwclock, hwclockfirst, hibernate-clean and hdparm,
     to get the bootlogger started earlier in the boot (Closes: #538936).
   * Extend the update-rc.d(8) manual page to document the new behaviour.
     Do not install translated update-rc.d manual pages until they
     are updated to reflect this.
   * Use versioned conflict on chkconfig (<< 11.0-79.1-2), now that it
     dropped the service command.
   * Drop unneeded dependency rmnologin from init.d/stop-bootlogd, and
     correct $remote_fs dependency to $local_fs, as /usr/ is not aused.
   * Drop unneeded dependency on udev for init.d/bootlogs, and add ldm
     and sdm to list of display managers to start after to get the
     complete list.
   * Extend boot order migration check to reject migration if init.d
     scripts from removed but not purged packages are present.
   * Add $syslog as a dependency for init.d/skeleton, as it should
     be used in the normal case.
   * Change init.d/urandom dependency from $local_fs to $remote_fs, as
     it uses /usr/bin/find to handle locally increased pool size
     (Closes: #543294).
   * Drop initscripts conflict on insserv (<< 1.09.0-12), now that
     sysv-rc depend on insserv (>> 1.12.0-10).
   * Drop initscripts conflict on udev (<< 0.080-1), which was
     before the current oldstable was released.
   * Drop initscripts conflict on usplash (<< 0.5.8-2), which was
     before the current stable was released.
   * Remove code in init.d/killprocs to restart /sbin/update, as it is
     only useful for kernels up to linux 2.2, which is no longer
     supported (Closes: #544249).  Thanks to Marco d'Itri for the tip.
   * Update Standards-Version from 3.8.2 to 3.8.3.  No changes needed.
   * Add code in initscripts.postrm to remove rc settings for init.d
     scripts on removal to follow policy and keep lintian happy, even
     though removing initscripts will leave the system unbootable.
     Update lintian overrides to reflect this.
   * Implement status argument to init.d/bootlogs, init.d/checkroot.sh,
     init.d/hostname.sh, init.d/rmnologin and init.d/urandom.
Checksums-Sha1: 
 df5efc1940674c5925fd2e96d5590467dc1a7be6 1501 sysvinit_2.87dsf-3.dsc
 43e9ebb44e66461ecbd4bce73eda638c78a95507 153269 sysvinit_2.87dsf-3.diff.gz
 dd6ff6386c0aa5a16147711caa7e0532953d68ea 105414 sysvinit_2.87dsf-3_i386.deb
 5c193ba38ec97333ccfb320d8e5e742ba474fedd 103840 sysvinit-utils_2.87dsf-3_i386.deb
 b807a934e565980677515b61b5d0b984d4534b13 77992 initscripts_2.87dsf-3_i386.deb
 87b8c135c32d76bf500026d78961f201a84e3a77 72524 sysv-rc_2.87dsf-3_all.deb
Checksums-Sha256: 
 3704315fdf2e0aac83090531bf0fd2423850a606543dd163a2e3a5a791ced975 1501 sysvinit_2.87dsf-3.dsc
 b7a9d90151cb6b8e32b872e0055436c033686b59240f83299d8961f1be294ae7 153269 sysvinit_2.87dsf-3.diff.gz
 0189ccfb3389203901a38175c5cf4607fe96cd8a3cfd89ce86ebc7e97357ca28 105414 sysvinit_2.87dsf-3_i386.deb
 07d65b04fb464081a178cf13cdbf34e4de2b8ff7459ab39bdfaceea0f36a7866 103840 sysvinit-utils_2.87dsf-3_i386.deb
 e89c11e105ff9574552ed921ee435bb257ae1b28e87a143eb8f27055803f5280 77992 initscripts_2.87dsf-3_i386.deb
 542c06f1c08484e75e1c18166ab744f24dd3fe4e3966e1cc4391eb24d75c77d4 72524 sysv-rc_2.87dsf-3_all.deb
Files: 
 ac4e643c444b9b176fbdecf3d87a6253 1501 admin required sysvinit_2.87dsf-3.dsc
 f0a5b043ce6aa2bc3dd2354d1403d412 153269 admin required sysvinit_2.87dsf-3.diff.gz
 ae108d2261520587abfd0d8f4a4886f7 105414 admin required sysvinit_2.87dsf-3_i386.deb
 1e8e3361d949252ca712bc6eb96dc6b3 103840 admin required sysvinit-utils_2.87dsf-3_i386.deb
 b50640313871f64a996cd960ef706da9 77992 admin required initscripts_2.87dsf-3_i386.deb
 ed39f9a4be2f1fb1995cd72d56b6be06 72524 admin required sysv-rc_2.87dsf-3_all.deb

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

iD8DBQFKojVB20zMSyow1ykRAuHpAKDezH7BJeXJyKONtigm4WoMdJeHlQCdG8lz
0fWhR9/+ILEWLs96H26LbNc=
=pNXj
-----END PGP SIGNATURE-----

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

From: Petter Reinholdtsen <pere@debian.org>

To: 538959-close@bugs.debian.org

Subject: Bug#538959: fixed in insserv 1.12.0-11

Date: Sat, 05 Sep 2009 11:32:09 +0000

Source: insserv
Source-Version: 1.12.0-11

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

insserv_1.12.0-11.diff.gz
  to pool/main/i/insserv/insserv_1.12.0-11.diff.gz
insserv_1.12.0-11.dsc
  to pool/main/i/insserv/insserv_1.12.0-11.dsc
insserv_1.12.0-11_i386.deb
  to pool/main/i/insserv/insserv_1.12.0-11_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 538959@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 insserv 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.8
Date: Sat, 05 Sep 2009 11:50:22 +0200
Source: insserv
Binary: insserv
Architecture: source i386
Version: 1.12.0-11
Distribution: unstable
Urgency: low
Maintainer: Petter Reinholdtsen <pere@debian.org>
Changed-By: Petter Reinholdtsen <pere@debian.org>
Description: 
 insserv    - Tool to organize boot sequence using LSB init.d script dependenci
Closes: 475478 511753 538959 540447 541613 542043
Changes: 
 insserv (1.12.0-11) unstable; urgency=low
 .
   [ Petter Reinholdtsen ]
   * Migrate the responsibility for enabling or disabling dependency
     based boot sequencing from the insserv package to the sysv-rc
     package.  Rewrite package description to reflect this (Closes:
     #475478, #511753, #538959).  Keep a dummy update-bootsystem-insserv
     script to avoid having to conflict with sysv-rc version 2.87dsf-2.
     Keep update-rc.d-insserv to make it impossible for the update-rc.d
     diversion to be a dangling link during upgrades.  Make it a copy
     of update-rc.d from the new sysv-rc version to make sure both
     behave the same way.  update-rc.d-insserv should be removed in
     Squeeze+1.  update-bootsystem-insserv could be removed when
     sysv-rc 2.87dsf-2 has been gone from unstable for 3 months.
   * Drop dependencies on sysv-rc, initscripts and sysvinit-utils, and
     leave it for sysv-rc to pull in the packages needed for dependency
     based boot sequencing to work properly.
   * Update README to reflect that dependency based boot sequencing is
     now the default in Debian.  Drop reference to obsolete CONCURRENCY
     setting (Closes: #540447).
   * Add new test case test_override_remove trying to reproduce bug #540866.
     No luck so far.
   * Add new test case test_insserv_virt_loop to reproduce a bug
     reported by Raphael Geissert, where an incorrect insserv.conf will
     make insserv hang forever.  Add new patch 94_v1_12_2.patch from
     upstream to fix it (Closes: #541613).
   * Correct test test_early_all to fail if $all do not work with stop
     sequences.  Add new patch 95_stop_all.patch from upstream to fix
     it (Closes: #542043).
   * Change the definition of $syslog to include rsyslog, sysklogd,
     dsyslog, inetutils-syslogd  and syslog-ng, to include all syslog
     implmenetations in the archive.  Dropped the syslog provide from
     the list, as it should not be used.
   * Update to Standards-Version 3.8.3, no changes required.
   * Add lintian override for the transitient update-bootsystem-insserv
     binary missing a manual page.
   * Add new test test_local_virtual to verify that local virtual
     facilities work properly.
 .
   [ Kel Modderman ]
   * Add new patch 20_install_perms_fixup.patch to install binary and
     conffile with correct permissions.
   * Add new patch 21_tests_suite_new_functions.patch to add a couple
     of new test suite functions to upstream test suite.
   * Make sure update-rc.d compares command line parameters for start/stop
     runlevel configuration with the Default-Start and Default-Stop values in
     LSB info comment of script and warns if there are differences.
Checksums-Sha1: 
 ca9588f5a19ecc21c1617cb87457d2f373d5ee71 1218 insserv_1.12.0-11.dsc
 8f05b8a8a8a254242158953d3c783c14bede0afb 58568 insserv_1.12.0-11.diff.gz
 19b5b7de996b201c3b79588b41c1439ab4933806 64818 insserv_1.12.0-11_i386.deb
Checksums-Sha256: 
 843ad5670be3ff6379403ec46da82c3345f0ba532efaa7a92345a05721681dc4 1218 insserv_1.12.0-11.dsc
 2abaed40777c76ad1544e38b5ff8ee080d9facd574c6210fbd78714c10c4b5b7 58568 insserv_1.12.0-11.diff.gz
 e2d23c08bfe099637fe8cfe980acbaade5b4052962d711d50c9fa3657ce321a5 64818 insserv_1.12.0-11_i386.deb
Files: 
 913e7ce0afdd0802820748e79ad87756 1218 misc optional insserv_1.12.0-11.dsc
 9a88a1a35a66360b1b9804f818deb4b8 58568 misc optional insserv_1.12.0-11.diff.gz
 62c7593bf804fee5352ad9b4e3b5373b 64818 misc optional insserv_1.12.0-11_i386.deb

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

iD8DBQFKokfm20zMSyow1ykRAv2tAKCjUkuQsyd3FhxIPlVdkSzurhRwbwCg4d8q
Bp4jittUNaJ16pZPjHNcmts=
=tu+f
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.