Red Hat Bugzilla – Bug 1305818
[pacemaker-libs-devel] pkgconfig files contain unresolved PACKAGE_URL
Last modified: 2016-05-10 19:52:50 EDT
# grep PACKAGE_URL /usr/lib*/pkgconfig/pacemaker*.pc
> /usr/lib64/pkgconfig/pacemaker-cib.pc:URL: @PACKAGE_URL@
> /usr/lib64/pkgconfig/pacemaker-cluster.pc:URL: @PACKAGE_URL@
> /usr/lib64/pkgconfig/pacemaker-fencing.pc:URL: @PACKAGE_URL@
> /usr/lib64/pkgconfig/pacemaker-lrmd.pc:URL: @PACKAGE_URL@
> /usr/lib64/pkgconfig/pacemaker.pc:URL: @PACKAGE_URL@
> /usr/lib64/pkgconfig/pacemaker-pengine.pc:URL: @PACKAGE_URL@
> /usr/lib64/pkgconfig/pacemaker-service.pc:URL: @PACKAGE_URL@
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.
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.