On Tue, Aug 18, 2009 at 09:24:56PM +0200, Micha Lenk wrote: > Karsten Hilbert wrote: > >> Did the boot order of the initscript get fixed on your last upgrade? > > > > Ah, probbably not, because I had it disabled during upgrade > > via rcconf. I only re-enabled it afterwards. > > > >[...] > > > > So it seems, no, it wasn't fixed. > > So, I guess you didn't read libchipcard-tools's NEWS.Debian.gz entry, > which should have indicated this possible little impediment to you: > > If you've modified the boot sequence for libchipcard-tools the > package's postinst script will not touch your modifications.
Well, one would have never guessed that enabling/disabling an init script via the Debian-recommended tool rcconf counts as "modifiying the boot *sequence*". > In this case please check manually that the chipcard daemon is > always started after HAL. > > As I understand it you have fixed your problem now. Hence, would you > agree to close the bug now? I haven't but if NEWS.Debian documents the algorithm it uses to fix the sequence when it *hasn't* been modified then I'd agree to close the bug. Certainly users can adjust the sequence any way they see fit but it is better to document what you *would* have done so users can do *that* manually so there's a better chance of re-syncing the state of affairs Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
