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 #1770235 +++
This bug was initially created as a copy of Bug #1768846
Description of problem:
* Tests /CoreOS/perl-DBD-Pg/Sanity/upstream-tests fail with the rebased libpq done for rhel-8.1.1.
* After talking to ppisar, it looks like the tests were fixed upstream (see https://bugzilla.redhat.com/show_bug.cgi?id=1768846#c5) and it looks like a good idea to fix this together with delivering postgresql:12 stream (tracked in bz#1721822) + libpq rebase in rhel-8.1.1 (tracked in bz#1749461)
* We still would like to keep bz#1768846 opened for libpq, because it still looks important enough for more investigation, but we're so far convinced the changes in that library do not change ABI, most probably just a slight change in behavior that perl-DBD-pg depended on changed, which should be not relevant nor visible for users.
How reproducible:
Always
Steps to Reproduce:
1. run tests for perl-DBD-Pg with the libpq-12.0 (/CoreOS/perl-DBD-Pg/Sanity/upstream-tests)
Actual results:
4 tests in 03dbmethod.t fails
Expected results:
No fail
Additional info:
see https://bugzilla.redhat.com/show_bug.cgi?id=1768846#c5
--- Additional comment from Honza Horak on 2019-11-08 14:45:09 GMT ---
Setting qa_test_coverage+ because the tests already exist.
[...]
--- Additional comment from Petr Pisar on 2019-11-11 09:32:40 GMT ---
We have perl-DBD-Pg twice in RHEL-8. Once as a non-modular package in BaseOS and once as a modular package of perl-DBD-Pg:3.7 stream in AppStream. We need to fix both of them.
[...]
--- Additional comment from Petr Pisar on 2019-11-14 09:24:19 GMT ---
There is also a request to pass perl-DBD-Pg tests against PostreSQL 12 server. As the server removes some features and a perl-DBD-Pg library uses them and the tests checks for them, it necessary to apply additional seven patches. These patches preserve perl-DBD-Pg API and all tests pass against PostregreSQL server 9.6, 10, and 12. I will include them referring to this bug report.
-----
perl-DBD-Pg:3.7 module is affected.
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, 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-2020:0347