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:

Please, provide perl-DBD-Pg package also in Client variant of RHEL6. As of now, it is available only for Server variant of RHEL-6.7, which prevents package pcp-pmda-postgresql from installation on Client, as it requires perl(DBD::Pg).


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

perl-DBD-Pg-2.15.1-4.el6_3
pcp-pmda-postgresql-3.10.9-6.el6


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Mapping packages to products is performed by release engineers.

I'm just curious, any chance of getting this one to RHEL-6.8?

This is by design

core packages for each variant are defined by supported comps groups. This package simply ends up in optional since it didn't get trough basic building blocks.

I'm marking it as NOTABUG unless we get a customer issue that they do really need that supported in client and explicit PM ack ...

We could also just drop all variants ;-)

Lubos

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days