Bug 155129
Summary: | Build requires eu-strip from elfutils | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Albert Strasheim <13640887> |
Component: | redhat-rpm-config | Assignee: | Paul Nasrat <nobody+pnasrat> |
Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | mattdm, n3npq, paul |
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: | 2006-08-14 18:35:45 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
Albert Strasheim
2005-04-16 18:25:35 UTC
This should be an requirement of rpm-build, not iptables. Assigning to rpm. eu-strip is mentioned only in /usr/lib/rpm/find-debuginfo.sh which is deliberately configured off in rpm- build in order to avoid the dependency. The dependency needs to be in redhat-rpm-config, not rpm-build, if you must have a dependency. This is needed for FC4 too. If/when the Fedora Extras buildsystem switches to the new version of mock that has a much smaller default package list, elfutils won't be included by default as there is nothing in the default package list that depends on elfutils. This will result in broken debuginfo packages and unstripped binaries for newly-built FE4 packages. Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you! Changing from FC3 to FC4. FC5 rpm-build has this dep already. Note that FC4 will enter legacy state in a few weeks, so if it isn't fixed in Core by then, it's incredibly unlikely to get fixed at all. (In reply to comment #6) > Note that FC4 will enter legacy state in a few weeks, so if it isn't fixed in > Core by then, it's incredibly unlikely to get fixed at all. True. I don't really expect it to get fixed, and it will have to be one of the issues worked around as described in Bug #196930 for building legacy packages in mock. As above, fixed in later rpm but not going to release an FC4 rpm update at this time. |