Bug 1305818
Summary: | [pacemaker-libs-devel] pkgconfig files contain unresolved PACKAGE_URL | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Pokorný [poki] <jpokorny> |
Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.5 | CC: | abeekhof, cfeist, cluster-maint, ivlnka, jpokorny |
Target Milestone: | rc | ||
Target Release: | 6.8 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | pacemaker-1.1.14-3.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-10 23:52:50 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: |
Description
Jan Pokorný [poki]
2016-02-09 10:19:15 UTC
Doesn't look it would be critical for anybody and the scope of PACKAGE_URL is pretty limited (basically [comment 0], nothing more). It would be more of a concern, if we were propagating that value in to the docs (which might be a good idea, to have a single point of authority). 6.9+ is pretty fine (or anytime a patch adding PACKAGE_URL in more serious context would be added). Fixed upstream as of d21fc64 There is one other minor change that would be good to get into 6.8, and if we can get approval for that, I'll try to combine this with it Bumping to 6.9 again, it turns out the other desired change is already in the current 6.8 build. Getting this in 6.8 after all because another issue came up. Fixed both as part of a new build for the rebase bz #1252206 since it's too late in the release cycle to do otherwise. Thanks! 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. https://rhn.redhat.com/errata/RHBA-2016-0856.html |