Package: insserv Version: 1.14.0-5 Severity: critical This bug completely breaks dist-upgrades, leaving the system in an indeterminate state. In my case, it resulted in being unable to use sudo from my account and having to completely reboot the box and use init=/bin/bash to recover.
This bug has been reported in various forms repeatedly, with insufficient severity each time. Examples of this type of breakage: #651037, #589238, #695751 Several packages have updated init scripts that will resolve the aparent dependency loops, such as: munin-node. However, insserv is installed before them during the dist-upgrade and fails installation due to the existing loops in the init scripts. Examples of this are: fetchmail and munin-node. The munin-node init script bug report is #680223. However, the updated package wasn't installed until after insserv. While I haven't found a bug report for the fetchmail issue, I did notice an updated init script being installed by it. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (900, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages insserv depends on: ii libc6 2.13-38 insserv recommends no packages. Versions of packages insserv suggests: pn bootchart2 <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
