On Wed, Oct 08, 2008 at 01:46:09PM +0200, Michael Matz wrote:

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.

My experience is that it's ldconfig medling with the library links. I doubt that it's a rpm bug. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On Wed, Oct 08, 2008 at 04:09:53PM +0200, Michael Matz wrote:

Hi,

On Wed, 8 Oct 2008, Michael Schroeder wrote:

...

...

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.

My experience is that it's ldconfig medling with the library links. I doubt that it's a rpm bug.

We will know once we see an strace. If the SONAMEs aren't completely unreasonable ldconfig shouldn't lead to the above situation either.

My guess is that /usr/lib/libcaca.so.0.99.15 has a soname of 0.99.14... M. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On Wed, Oct 08, 2008 at 06:30:34PM +0200, Christian Morales Vega wrote:

2008/10/8 Michael Schroeder :

...

On Wed, Oct 08, 2008 at 04:09:53PM +0200, Michael Matz wrote:

...

We will know once we see an strace. If the SONAMEs aren't completely unreasonable ldconfig shouldn't lead to the above situation either.

My guess is that /usr/lib/libcaca.so.0.99.15 has a soname of 0.99.14...

strace available at http://www.filefactory.com/file/9941bc/n/rpm_test_bz2 ldconfig is who changes the /usr/lib/libcucul.so.0 symlink to point to libcucul.so.0.99.14 (line 10653 of strace) rpm previously has correctly set it to libcaca.so.0 (line 3615). But rpm first calls ldconfig and *after* unlinks libcucul.so.0.99.14, "confusing" ldconfig. I don't know how the update process in rpm or ldconfig are supposed to work, but is this normal?

Yes, that's perfectly normal. Ah, you're symlinking library names. Though, I never was successful with that. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org