RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

# 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@

Proposed fix:
https://github.com/ClusterLabs/pacemaker/pull/914/

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