On Wed, Oct 08, 2008 at 06:30:34PM +0200, Christian Morales Vega wrote:
2008/10/8 Michael Schroeder <mls@suse.de>:
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