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:
All libabigail packages including debug, source and all architectures are not correctly signed.

Version-Release number of selected component (if applicable):
libabigail-1.8.2-3.el9
In compose RHEL-9.2.0-20221020.2

Steps to Reproduce:
rpm -q --qf '%{sigpgp:pgpsig}\n' -p libabigail-1.8.2-3.el9.aarch64.rpm 

Actual results:
warning: libabigail-1.8.2-3.el9.aarch64.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
(none)

Expected results:
Something like: RSA/SHA256, Wed 19 Oct 2022 10:48:58 AM CEST, Key ID 199e2f91fd431d51

Could the problem be with brew/koji build system rather than libabigail? Seems like the build system would be responsible for signing the rpms.

 libabigail-2.1-2.el9 was built 20221102.  Downloaded the libabigail-2.1-2 from the RPMs from the nightly CRB composes and see signatures in the newer RPMs:

[wcohen@haro Downloads]$ rpm -q --qf '%{sigpgp:pgpsig}\n' -p  libabigail-2.1-2.el9.x86_64.rpm 
warning: libabigail-2.1-2.el9.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
RSA/SHA256, Wed 02 Nov 2022 07:54:40 AM EDT, Key ID 199e2f91fd431d51
[wcohen@haro Downloads]$ rpm -q --qf '%{sigpgp:pgpsig}\n' -p  libabigail-2.1-2.el9.aarch64.rpm 
warning: libabigail-2.1-2.el9.aarch64.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
RSA/SHA256, Wed 02 Nov 2022 07:54:36 AM EDT, Key ID 199e2f91fd431d51

Verified with libabigail-2.1-2.el9.

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 (libabigail bug fix and enhancement update), 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-2023:2590