On 08/05/2009 01:50 PM, Miroslav Lichvar wrote:
On Wed, Aug 05, 2009 at 10:45:20AM -0500, Rex Dieter wrote:
On 08/05/2009 10:07 AM, Miroslav Lichvar wrote:
I've recently come across an ldconfig issue when updating libraries.
Apparently rpm doesn't always call ldconfig in %postun, I've filed bug
#513224 for that. It doesn't seem to be a real bug though.
Interesting, might this be related to the odd symlinks changing problem
in qt as well?
https://bugzilla.redhat.com/show_bug.cgi?id=510246
I think it is. And this one is even better as calling /sbin/ldconfig
afterwards doesn't revert it.
Before ldconfig call in qt %post:
/usr/lib64/libQtCore.so -> libQtCore.so.4.5.0
/usr/lib64/libQtCore.so.4 -> libQtCore.so.4.5.2
/usr/lib64/libQtCore.so.4.5 -> libQtCore.so.4.5.2
/usr/lib64/libQtCore.so.4.5.0
/usr/lib64/libQtCore.so.4.5.2
/usr/lib64/libQtCore_debug.so -> libQtCore.so
After:
/usr/lib64/libQtCore.so -> libQtCore.so.4.5.0
/usr/lib64/libQtCore.so.4 -> libQtCore_debug.so
/usr/lib64/libQtCore.so.4.5 -> libQtCore.so.4.5.2
/usr/lib64/libQtCore.so.4.5.0
/usr/lib64/libQtCore.so.4.5.2
/usr/lib64/libQtCore_debug.so -> libQtCore.so
It seems that ldconfig is comparing everything (including symlinks)
providing libQtCore.so.4 and libQtCore_debug.so comes out as last. It
doesn't point to the same file as the original symlink, so it's
changed. Using ldconfig -X should avoid it.
OK, then, for the love of all that is holy, let's get -X using asap.
Followup, why isn't -X the default behavior?
-- Rex
--
Fedora-packaging mailing list
Fedora-packaging@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-packaging
