Marcus Brinkmann writes: > I think this is only linker confusion and has its cause by removing > libraries and symlinks and running ldconfig in the wrong order.
> Policy about calling ldconfig in package scripts is changing at the moment, > and we hope to have the proper solution implemented for 2.1. > However, I don't think this is an indication for left-overs. Can you try > running ldconfig again after dpkg has finished its job? I believe the problem is not in dpkg's ldconfig order... nr# ldconfig ldconfig: warning: can't open /usr/lib/i486-linuxaout/libdb.so.1 (No such file or directory), skipping ldconfig: warning: can't open /usr/lib/libext2fs.so (No such file or directory), skipping ldconfig: warning: can't open /usr/lib/libe2p.so (No such file or directory), skipping ldconfig: warning: can't open /usr/lib/libuuid.so (No such file or directory), skipping > Thank you, > Marcus > -- > "Rhubarb is no Egyptian god." Debian GNU/Linux finger brinkmd@ > Marcus Brinkmann http://www.debian.org master.debian.org > [EMAIL PROTECTED] for public PGP Key > http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09 -- Luiz Otavio L. Zorzella Product Engineer [EMAIL PROTECTED] http://www.conexware.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]