Package: lsb-base Version: 4.1+Debian5 Severity: critical Justification: breaks the whole system
When run with 'set -u', sourcing init-functions fails: steve@localhost:~$ dash \u@\h:\w$ set -u \u@\h:\w$ . /lib/lsb/init-functions dash: 428: /lib/lsb/init-functions: FANCYTTY: parameter not set The init scripts for mdadm have 'set -eu', and fail to upgrade: Preparing to replace mdadm 3.2.4-1 (using .../mdadm_3.2.5-1_amd64.deb) ... /etc/init.d/mdadm: 428: /lib/lsb/init-functions: FANCYTTY: parameter not set invoke-rc.d: initscript mdadm, action "stop" failed. dpkg: warning: subprocess old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... /etc/init.d/mdadm: 428: /lib/lsb/init-functions: FANCYTTY: parameter not set invoke-rc.d: initscript mdadm, action "stop" failed. dpkg: error processing /var/cache/apt/archives/mdadm_3.2.5-1_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 2 Severity critical as the mdadm-raid script will fail to start as well, thus not bringing the raid arrays up. (Oddly that script doesn't get called on upgrade, so fixing just the script that gets the dpkg-blocking error could probably still leave an unbootable system). I'll log another bug on mdadm, as using "set -e" is a bug (for the reasons in #661002). But lsb-base is the one that's just been upgraded, so it's the one that needs the apt-listbugs warning. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
