Bug 488183
Summary: | mkinitrd fails with: "cp: cannot stat `/usr/lib64//libparted-1.8.so.8.0.0': No such file or directory" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Ellson <john.ellson> |
Component: | mkinitrd | Assignee: | Peter Jones <pjones> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | hdegoede, katzj, pjones, wtogami |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-05-25 08:24:24 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
John Ellson
2009-03-03 02:21:53 UTC
Can you do "ls -l /usr/lib64/libparted*" please and paste the output here? I think you've got a dangling libparted-1.8.so.8 symlink under there. root@ontap:~# yum reinstall parted ... Removed: parted.x86_64 0:1.8.8-14.fc11 Installed: parted.x86_64 0:1.8.8-14.fc11 Complete! root@ontap:~# ls /usr/lib*/libpart* /lib*/libpart* /lib64/libparted-1.8.so.8 /usr/lib64/libparted-1.8.so.8 /lib64/libparted-1.8.so.8.0.0 /usr/lib64/libparted.so root@ontap:~# sorry, that was supposed to be ls -l... the two in /usr/lib64 were softlinks, but not dangling I just did: # rm /usr/lib*/libpart* /lib*/libpart* # yum reinstall parted now the links in /usr/lib64/ are gone. Looks like parted rpm isn't cleaning up properly. mkinitrd seems happier now ... rebooting .... Ok, I think you've hit some packaging bug in parted, closing as not a bug (because it is not an mkinitrd bug). Ok, so I can reproduce this now, and this is a real issue, re-opening and then closing as a dup of the bug were this will be tracked, please see that bug for more details and add yourself to the CC if you want to kept up2date. *** This bug has been marked as a duplicate of bug 502221 *** |