Hi, On Fri, 3 Oct 2008, Christian Morales Vega wrote:
....L... /usr/lib/libcaca.so.0 ....L... /usr/lib/libcucul.so.0
$ rpm -qvl libcaca0 lrwxrwxrwx 1 root root 18 sep 30 21:26 /usr/lib/libcaca.so.0 -> libcaca.so.0.99.15 lrwxrwxrwx 1 root root 12 sep 30 21:26 /usr/lib/libcucul.so.0 -> libcaca.so.0 $ l /usr/lib/libc[au]c* lrwxrwxrwx 1 root root 13 oct 3 01:31 /usr/lib/libcaca.so.0 -> libcucul.so.0 -rwxr-xr-x 1 root root 675948 sep 30 21:26 /usr/lib/libcaca.so.0.99.15* lrwxrwxrwx 1 root root 19 oct 3 01:31 /usr/lib/libcucul.so.0 -> libcucul.so.0.99.14
That's even a broken link (libcucul.so.0.99.14 doesn't exist). I think that's pretty clearly an RPM bug. The generated files don't match what's in the rpm. Hmm, or (just maybe) it might be ldconfig breaking this. E.g. rpm installing the files and softlinks just fine, but then ldconfig (perhaps mislead by wrong SONAMEs in the DSOs) generates wrong targets? On reflection this can't really happen, but something to try. Perhaps an strace of rpm while updating this package reveals something interesting.
So, there is something about symbolic links and updates that I should know or this is a RPM bug?
The latter I think. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org