Bug 188062
Summary: | ldconfig complains about /usr/lib/libhesiod.so.0 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Horst H. von Brand <vonbrand> |
Component: | prelink | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | chkr, davej, jik, jneedle, jnovy, nicolas.mailhot, reuben-redhatbugzilla |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 0.3.8-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-06-21 11:08:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Horst H. von Brand
2006-04-05 17:21:34 UTC
Can you run "rpm -V hesiod" on your system to verify that the package is properly installed? On my systems, it actually is a symlink, and the RPM package (checked with "rpm -qlv") lists it as one as well. [root@laptop11 ~]# rpm -V hesiod SM5..... /usr/lib/libhesiod.so.0 Something's fishy... OK, installed the package again, rpm(1) and ldconfig(8) are happy. Thanks! You're not alone, I had the same issue. Something is wrong here. libhesiod.so.0.0.0 and libhesiod.so.0 have both been regular files on my system, but with different filelengths. I've reinstalled hesiod and everything is ok now. Just as here, the .0 is slightly longer and has the same timestamp. Perhaps something in the upgrades is overwriting the symlink? CCing the anaconda team, in case they can provide a clue as to what's going on here. I just updated from FC5 to rawhide hesiod and didn't see this. Is there a reproducible path for getting this? OK between updating yesterday and today with a prelink run inbetween I got the same failure. I rpm -V'd post install yesterday. I can replicate: [root@enki ~]# prelink -av -mR <stuff> [root@enki ~]# rpm -Vv hesiod ......... /usr/lib/libhesiod.so.0 ......... /usr/lib/libhesiod.so.0.0.0 ......... /usr/share/doc/hesiod-3.1.0 ......... d /usr/share/doc/hesiod-3.1.0/NEWS ......... d /usr/share/doc/hesiod-3.1.0/README ......... d /usr/share/man/man5/hesiod.conf.5.gz [root@enki ~]# prelink -u /usr/lib/libhesiod.*so* prelink: /usr/lib/libhesiod.so does not have .gnu.prelink_undo section [root@enki ~]# rpm -Vv hesiod SM5...... /usr/lib/libhesiod.so.0 ......... /usr/lib/libhesiod.so.0.0.0 ......... /usr/share/doc/hesiod-3.1.0 ......... d /usr/share/doc/hesiod-3.1.0/NEWS ......... d /usr/share/doc/hesiod-3.1.0/README ......... d /usr/share/man/man5/hesiod.conf.5.gz *** Bug 189565 has been marked as a duplicate of this bug. *** Happens on my system too - every day it seems - noticeable after a yum update to rawhide. I'm on x86_64, so this is not i386 specific. Should be fixed in prelink-0.3.7-1. *** Bug 145983 has been marked as a duplicate of this bug. *** *** Bug 193175 has been marked as a duplicate of this bug. *** One question: Will this fix be backported to FC5, too? Because my bug report against FC5 was closed as duplicate of this bug (which is already closed), but the problem still persists. Hi Jakub, (In reply to comment #11) > Should be fixed in prelink-0.3.7-1. I'm sorry for the bug spam, but I didn't got an answer to my question for one week. Please can you give a short statement whether the fix will be backported to FC5 or which steps are necessary to achieve this? Thank you very much for your help. (In reply to comment #11) > Should be fixed in prelink-0.3.7-1. Isn't. Still the same here (rawhide, i386). Have you downgraded hesiod, prelinked, upgraded hesiod and prelinked again to verify? No prelink change can retroactively change what the bug caused, it has no means to find out something should have been a symlink (to what) rather than a file. I just did the following: rm /usr/lib/libhesiod.so.0 ldconfig prelink --all Now it is not a file anymore. But I've done the first two a few times, and during the next update the complaints are back. prelink-0.3.8-1 contains a better fix for this problem. |