There is somehow a glitch we have to solve in the pre/post-inst/rm
scripts for ncurses and potentially for readline.
My bash is now (and should be in the future, maybe even with shared
readline):
[EMAIL PROTECTED]:tty1:/lib# ldd /bin/bash
libncurses.so.3.0 => /lib/libncurses.so.3.0
libc.so.5 => /lib/libc.so.5.2.18
and don't like to be invoked without libncurses.so.3.0 handy. Is it
really ok to move libncurses.so.3.0 to libncurses.so.3.0.new in pre
--- why is this TRT? Upgrading libc
5.2.16-1 -> 5.2.16-2 -> 5.2.16-3 -> 5.2.18-0
seems to work, but ncurses
3.0-1.9.8a-2 -> 3.0-1.9.8a-3 -> 3.0-1.9.8a-3
left me with /lib/libncurses.3.0.new but without /lib/libncurses.3.0.
This has to be avoided at all costs!
mfg
Rolf Rossius
[EMAIL PROTECTED]:tty3:/fs7/debian/binary/base# dpkg -i ncurses3.0-1.9.8a-3.deb
(Reading database ... 7711 files and directories currently installed.)
Preparing to replace ncurses3.0 (using ncurses3.0-1.9.8a-3.deb) ...
sh: can't load library 'libncurses.so.3.0'
dpkg: error processing ncurses3.0-1.9.8a-3.deb (--install):
subprocess pre-installation script returned error exit status 16
sh: can't load library 'libncurses.so.3.0'
dpkg: error while cleaning up:
subprocess post-installation script returned error exit status 16
Errors were encountered while processing:
ncurses3.0-1.9.8a-3.deb
