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.

Description of problem:

The soname of libpapi is libpapi.so (without a version number).  That's obviously wrong, but it specifically breaks anything using it if you have another version of papi installed (in my case as an SCL), e.g. for Lustre support (#1262015).

$ readelf -d /usr/lib64/libpapi.so* | grep SONAME
 0x000000000000000e (SONAME)             Library soname: [libpapi.so]
 0x000000000000000e (SONAME)             Library soname: [libpapi.so]
 0x000000000000000e (SONAME)             Library soname: [libpapi.so]

Version-Release number of selected component (if applicable):

papi-5.1.1-11.el6.x86_64

The lack of so version for the older papi library is not ideal. Changing it to be versioned may break existing code customer code already linked with this particular library, so versioning it is not really an option.

You should take a look at how the RHEL-6 pcp srpm package is built to use access an alternative version papi libraries. It uses the papi-5.1.1 libraries on RHEL-6 without issue.