Hi, This is a minor annoyance, but it always bothers me. When upgrading or reconfiguring, I chronically end up with "orphaned" lines in /etc/ld.so.conf.
ie. Currently, on my main Pentium system... ldconfig: warning: can't open /usr/X11R6/lib/libgtk.so.1.0 (No such file or directory), skipping ldconfig: warning: can't open /usr/X11R6/lib/libgdk.so.1.0 (No such file or directory), skipping ldconfig: warning: can't open /usr/openwin/lib/libgtk.so.1.0 (No such file or directory), skipping ldconfig: warning: can't open /usr/openwin/lib/libgdk.so.1.0 (No such file or directory), skipping Currently, on my 386 system... ldconfig: warning: can't open /usr/local/lib (No such file or directory), skipping 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/libpthread.so (No such file or directory), skipping ldconfig: warning: can't open /usr/lib/libjpeg.so.6a (No such file or directory), skipping It's easy enough to fix, just edit the /etc/ld.so.conf file and remove the offending "orphaned" lines. Anyways, I'm sure this is a chronic annoying problem everyone is experiencing. Is the cause is due to incorrect packaging of the shared libraries? I'm not sure. I'm just wondering if there is a way of automatically cleaning up after those (buggy?) packages are long gone... Or perhaps we need to enforce policy a bit better. If somebody could explain what exactly is going wrong in these packages - ie. what policy are they violating? Or is it dpkg's fault? Cheers, - Jim
pgpxieJE6BPVo.pgp
Description: PGP signature
