Red Hat Bugzilla – Bug 543
libjpeg-6b-5 orphans file /usr/lib/libjpeg.so.62
Last modified: 2016-09-19 13:04:23 EDT
Looking for the package that owned /usr/lib/libjpeg.so.62 I
found it to not belong to any package, although it does come
Here is a session transcript:
cafe:bash# rm /usr/lib/libjpeg.so.62
rm: remove /usr/lib/libjpeg.so.62'? y
cafe:bash# rpm -U --force libjpeg-6b-5.i386.rpm
cafe:bash# ls -l /usr/lib/libjpeg.so.62*
lrwxrwxrwx 1 root root 17 Dec 20 14:07
/usr/lib/libjpeg.so.62 -> libjpeg.so.62.0.0
-rwxr-xr-x 1 root root 136927 Jun 9 1998
cafe:bash# rpm -qf /usr/lib/libjpeg.so.62
file /usr/lib/libjpeg.so.62 is not owned by any package
I believe that is a normal behavior - symlink is not a part of the
RPM, but it is created by the ldconfig which is executed in the
postinstall script. If you want to know where the library came from,
you can always run rpm -qf on the library itself instead of the
I tested this, and yes ldconfig does create the symlink. However
other packages will have dependancies on that particular file, and the
package (libjpeg-6b-5) provides this file.
Perhaps the packages that have symlinks created by external programs
from the postinstall scripts should report that the symlinks are
included with the package?
The symlink /usr/lib/libjpeg.so.62 is generated by running
/sbin/ldconfig in the %post step installing the rpm. There
is no obvious (to me) problem with having the link generated
rather than owned.
Commit pushed to master at https://github.com/openshift/origin-web-console
Improving consistency of .data-toolbar display...
across monitoring, events, and other resources pages, which also
resolves issue #543.