Bug 950748
Summary: | /lib64/libproc.so package both in procps and procps-devel, unable to build packages depending on it | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Simone Caronni <negativo17> | |
Component: | procps | Assignee: | Jaromír Cápík <jcapik> | |
Status: | CLOSED ERRATA | QA Contact: | Martin Frodl <mfrodl> | |
Severity: | high | Docs Contact: | ||
Priority: | medium | |||
Version: | 6.5 | CC: | albert, mfrodl, ovasik, pikachu.2014, pknirsch, pmatilai | |
Target Milestone: | rc | Keywords: | EasyFix | |
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | procps-3.2.8-26.el6 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1119255 (view as bug list) | Environment: | ||
Last Closed: | 2014-10-14 08:21:52 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 905255, 1119255 |
Description
Simone Caronni
2013-04-10 19:20:08 UTC
Building packages with mock or koji produces the error. Hello, any news on this? Thanks, --Simone This clearly is a packaging bug and should be fixed, but there are rpm bugs at play as well: 1) Permission mode bits are not applicaple to symlinks, but rpmbuild lets %attr and %defattr affect the mode of symlinks 2) rpm >= 4.10 considers different permission mode as a conflict. Symlinks have no meaningful mode and they normally never conflict but due to 1) packaged symlinks can have irregular mode bits set, causing the conflict. Mode bits on symlinks should not be considered when determining file conflicts. Both 1 and 2 have now been fixed rpm upstream and can be expected to land in Fedora soonish, which will make the conflict go away. Hello Simone, thanks for this bugreport. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution. If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization to assure a timely resolution. For information on how to contact the Red Hat production support team, please visit: https://www.redhat.com/support/process/production/#howto (This should answer your question on fedora-devel list) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1595.html |