Bug 221049

Summary: glibc-devel package contains broken links
Product: [Fedora] Fedora Reporter: Christian Krause <chkr>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-01-02 17:44:51 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Christian Krause 2006-12-31 03:49:55 EST
Description of problem:
glibc-devel contains a symbolic link
/usr/lib/librt.so.1 -> librtkaio.so
which points to a non-existing file

Version-Release number of selected component (if applicable):
glibc-devel-2.5-3.i386.rpm

How reproducible:
100%

Steps to Reproduce:

root@computer:/etc# rpm -U /fedora-core/6/i386/os/Fedora/RPMS/glibc-2.5-3.i686.rpm
 /fedora-core/6/i386/os/Fedora/RPMS/glibc-devel-2.5-3.i386.rpm --force

root@computer:/etc# rpm -V glibc glibc-devel

root@computer:/etc# ls -la /usr/lib/librt*
-rw-r--r-- 1 root root 52128 Oct  8 17:10 /usr/lib/librt.a
-rw-r--r-- 1 root root 59038 Oct  8 17:10 /usr/lib/librtkaio.a
lrwxrwxrwx 1 root root    20 Dec 31 09:42 /usr/lib/librt.so -> ../../lib/librt.s
o.1
lrwxrwxrwx 1 root root    12 Dec 31 09:42 /usr/lib/librt.so.1 -> librtkaio.so

root@computer:/etc# /sbin/ldconfig 

root@computer:/etc# ls -la /usr/lib/librt*
-rw-r--r-- 1 root root 52128 Oct  8 17:10 /usr/lib/librt.a
-rw-r--r-- 1 root root 59038 Oct  8 17:10 /usr/lib/librtkaio.a
lrwxrwxrwx 1 root root    20 Dec 31 09:42 /usr/lib/librt.so -> ../../lib/librt.s
o.1

root@computer:/etc# rpm -V glibc glibc-devel
missing     /usr/lib/librt.so.1

Actual results:
before ldconfig call:
- librt.so.1 is a broken link
after ldconfig call
- librt.so.1 is missing (deleted by ldconfig)

Expected results:
glibc-devel should contain the correct symbolic link and after ldconfig the
glibc-devel package should be consistent with the file system (rpm -V glibc-devel)
Comment 1 Jakub Jelinek 2007-01-02 17:44:51 EST

*** This bug has been marked as a duplicate of 213555 ***