Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1966693 +++
Description of problem:
In the gcc-toolset-10 software collection, two devel packages have pkgconfig virtual provides.
- gcc-toolset-10-elfutils-devel provides pkgconfig(libdw)
- gcc-toolset-10-valgrind-devel provides pkgconfig(valgrind)
Based on the SCL guidelines [0], this appears to be incorrect. I noticed this because mesa has a build requirement on pkgconfig(valgrind) that is resolving to gcc-toolset-10-valgrind-devel instead of valgrind-devel [1]. This is also the case in the equivalent gcc-toolset-9 packages. I'm reporting this against gcc-toolset-10 because currently that is the only one which has a package NVR high enough to cause an issue, but this needs to be fixed in both collections.
Version-Release number of selected component (if applicable):
gcc-toolset-10-elfutils-devel-0.182-3.el8
gcc-toolset-10-valgrind-devel-3.16.0-4.el8
gcc-toolset-9-elfutils-devel-0.176-5.el8
gcc-toolset-9-valgrind-devel-3.15.0-9.el8
How reproducible:
always
Steps to Reproduce:
1. dnf install 'pkgconfig(valgrind)'
Actual results:
resolves to gcc-toolset-10-valgrind-devel
Expected results:
resolves to valgrind-devel
Additional info:
[0] https://www.softwarecollections.org/en/docs/guide/#sect-Software_Collection_Automatic_Provides_Requires_Filtering_Support
[1] https://koji.mbox.centos.org/pkgs/work/tasks/3443/253443/root.log
--- Additional comment from Mark Wielaard on 2021-06-02 12:14:13 UTC ---
OK, if I understand correctly we don't want the automatic pkgconfig provides for gcc-toolset packages when those same pkgconfig provides are also in the base system.
So we need to add something like:
%{?scl:%filter_from_provides s|pkgconfig|%{?scl_prefix}pkgconfig|g}
%{?scl:%filter_setup}
To the elfutils.spec and valgrind.spec.
I'll keep this bug for elfutils and clone this bug for valgrind to track both packages.
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 (new packages: gcc-toolset-11-valgrind), 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://access.redhat.com/errata/RHBA-2021:4263