Package: insserv Severity: important
The following happened to me: I installed insserv, it reordered the init scripts successfully. Then I uninstalled a package (in my case it was bootchart). After that, I also decided to uninstall insserv again. insserv completely broke down, as it couldn't find the bootchart init script anymore. Instead it tried to reconfigure all packages that ship an init script. This completely blew up my system, when it tried to restart udev. insserv should be much more careful when it is removed again. If an init script is no longer present, it should simply skip it and not recreate the symlinks again. If a package is installed after insserv was activated (ie insserv has no backup of the init script priorities), it should only reconfigure this one package. An even better alternative would be, if update-rc.d would store/save those priories in the backup for new packages. Michael -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24.4 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages insserv depends on: ii debconf [debconf-2.0] 1.5.20 Debian configuration management sy ii libc6 2.7-10 GNU C Library: Shared libraries ii sysv-rc 2.86.ds1-55 System-V-like runlevel change mech insserv recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
