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:
RHEL6 doesn't seem to have a separate -devel subpackage:
$ sudo yum install valgrind-devel
No package valgrind-devel available.
Error: Nothing to do

... and yet, the header files such as valgrind/memcheck.h are not present in the
base package.  This means programs that include valgrind client requests cannot be
compiled, which makes the RHEL6 package completely useless for my purposes.

Version-Release number of selected component (if applicable):
valgrind-3.8.1-3.2.el6.x86_64

How reproducible:
100% I imagine

Steps to Reproduce:
1. see description

I pulled down the RHEL6 SRPM and verified that the specfile knows about building the devel subpackage, so actually this bug probably belongs to distribution.  My memory is fuzzy about exactly who gets the blame though ...

It is available from the rhel-x86_64-server-optional-6 repository.

Hello,

as mentioned most of -devel packages are placed in the optional channels. Optional channel is available to any RHEL subscriber, it's just not turned on by default.

I'm marking this issue as not a bug.

Thanks for understanding

Lubos