Package: lsb-base
Version: 3.1-16
Severity: critical
Tags: patch
Justification: breaks unrelated software
The lsb-base 3.1-16 has a problem with the FANCYTTY option.
When you try to upgrade by example mysql-server-5.0 an error happends:
Preparing to replace mysql-server-5.0 5.0.24a-4 (using
.../mysql-server-5.0_5.0.24a-5_i386.deb) ...
Stopping MySQL database server: mysqld/lib/lsb/init-functions: line 134:
FANCYTTY: unbound variable
invoke-rc.d: initscript mysql, action "stop" failed.
dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
Stopping MySQL database server: mysqld/lib/lsb/init-functions: line 134:
FANCYTTY: unbound variable
invoke-rc.d: initscript mysql, action "stop" failed.
dpkg: error processing
/var/cache/apt/archives/mysql-server-5.0_5.0.24a-5_i386.deb (--unpack):
subprocess new pre-removal script returned error exit status 1
Stopping MySQL database server: mysqld/lib/lsb/init-functions: line 134:
FANCYTTY: unbound variable
invoke-rc.d: initscript mysql, action "stop" failed.
Starting MySQL database server: mysqld/lib/lsb/init-functions: line 134:
FANCYTTY: unbound variable
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error while cleaning up:
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/mysql-server-5.0_5.0.24a-5_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
This is maybe because the change:
if [ FANCYTTY = 0 ]; then
to:
if [ -z $FANCYTTY ]; then
At the bottom of /lib/lsb/init-functions change:
[ -e /etc/lsb-base-logging.sh ] && . /etc/lsb-base-logging.sh || true
to:
if [ -e /etc/lsb-base-logging.sh ]; then
. /etc/lsb-base-logging.sh || true
else
FANCYTTY=
fi
or:
FANCYTTY=
[ -e /etc/lsb-base-logging.sh ] && . /etc/lsb-base-logging.sh || true
In the first option if no /etc/lsb-base-logging.sh exists FANCYTTY will be
declared as an empty string.
In the second option FANCYTTY is declared and after the
/etc/lsb-base-logging.sh is executed.
The "real" resolution of the problem should be a configuration file.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=es_MX, LC_CTYPE=es_MX (charmap=ISO-8859-1)
Versions of packages lsb-base depends on:
ii ncurses-bin 5.5-4 Terminal-related programs and man
ii sed 4.1.5-1 The GNU sed stream editor
lsb-base recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
