Am 19.07.2010 00:20, schrieb Petter Reinholdtsen:
[Ralph Ulrich]
Is update-rc.d really usable as a trigger like kernel related
"update-initramfs" is used:
- deferrable
- all of the previous configuration obsoleted and removed
I considered using triggers to update the boot sequence, but decided
against it because it not ensure the boot sequence is consistent after
upgrades. I believe it is better that a inconsistent boot sequence
casues imediate failure instead of trying to clean up the mess after
the init.d scripts have been replaced.
My guess is the other way round: The mess occures because of that. Quiet
sure you have been through this all, what you mention here, during the
first time of introduction of insserv to Debian: All the LSB-headers had
to be written from scratch.
If there were some quick tests available at begin of the trigger?
Why did I saw this debootstrap problem: Debootstrap failed because
of a service couldn't install without a yet installed
Required-Start.
Sound like a bug in some package. Only one I remember having such bug
recently was util-linux, and that bug was luckily solved after a few
days. Is there some new bug around now?
At http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581420#5
---
Selecting previously deselected package util-linux.
O: dpkg: regarding .../util-linux_2.17.2-1_amd64.deb containing
util-linux, pre-dependency problem:
O: util-linux pre-depends on libblkid1 (>= 2.17.2)
O: libblkid1 is unpacked, but has never been configured.
---
Last line sounds to me that a triggered insserv after unpacking all
packages during the dbootstrap would have prevented this bug.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
