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.
We're trying to get any version of qpdf built for CentOS Stream so that we can generate a working compose.
Based on an email discussion we think that changes to zlib may be causing troubles in the test suite for qpdf causing it to FTBFS.
Here's a link to a qpdf build:
https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=214153
Hi, thanks for the report. Seems strange to me, can you point to the last version of zlib, which successfully builds with qpdf ? Maybe we can isolate the problem somewhere.
The last update should have no impact on the functionality or output of zlib. It's just fixing some minor issues found by covscan:
https://src.fedoraproject.org/rpms/zlib/c/59fb3beffd40fc92202a025c761ddbc469133063?branch=rawhide
Before that, there were some changes, but only for aarch64 architectures, which should not have impact on s390x arch.
https://src.fedoraproject.org/rpms/zlib/c/c95d3d1e735ec5acd3b2b27d64ad4530a19e9049?branch=rawhide
If only s390x architecture is a problem, we might have a problematic patch. We are currently maintaining multiple downstream s390x arch patches. If these patches are problematic, we need to discuss the changes with IBM, who authored the patches.
If you can provide us some more information about the issue, it will help us with investigating the problem.
Thanks.
Ondrej
Results of investigation:
There is a change of behavior in zlib on s390x architectures. After applying s390x-only dowstream patches which enable Z-accelerated inflate and deflate (maintained by IBM), there are some minor changes in error messages. This change leads to test failure in qpdf, as it compares the expected error message with the actual one. There is no bug in zlib, nor qpdf.