In message <[EMAIL PROTECTED]> you wrote: [snip] >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 direct >ory), skipping >ldconfig: warning: can't open /usr/lib/libpthread.so (No such file or >directory), skippi >ng >ldconfig: warning: can't open /usr/lib/libjpeg.so.6a (No such file or >directory), skippi >ng [snip] >Is the cause is due to incorrect packaging of the shared >libraries? I'm not sure.
Yes, I think so. BTW, I agree this is very annoying. >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? Yes, it is discussed in the Debian Packaging Manual, section 12. See: /usr/doc/dpkg/packaging.html/ch-sharedlibs.html You should just go ahead and file bugs against packages which don't include the .so link as part of the package. .....A. P. [EMAIL PROTECTED]<URL:http://www.onShore.com/> -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
