+++ 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.