I can confirm this bug.
It seems that *all* scripts in /etc/init.d/ exit with a status of 1,
regardless of whether an error has actually happened or not.
Moving /etc/lsb-base-logging.sh out of the way (ie. renaming or removing
it) solves the problem.
I am not sure, but is it sane to have any return value other than 0 in
that script? Right now this script breaks a lot of things, including
updates of packages that contain init scripts.
-- Stephan
r...@sp-desktop:~# apt-cache policy splashy
splashy:
Installed: 0.3.13-4
Candidate: 0.3.13-4
Version table:
*** 0.3.13-4 0
100 /var/lib/dpkg/status
0.3.13-3 0
500 http://ftp.at.debian.org lenny/main Packages
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
