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.
Created attachment 527292[details]
Patch which partially fixes the signing already signed packages problem.
rpm-4.8.0 has backported broken change c0aad81e9b17afcbea4008485d354673495eb148 from rpm.org rpm git. That was supposed to fix #488953 but actually introduced even worse regression.
When you try to sign packages in directory like:
rpm --resign *.rpm
rpm will exit with result code 0 when it finds first package which is correctly signed. This leaves very big possibility that you have dir of packages, only first ones being signed.
rpm should actually only skip without modifications already singed packages.
I attach patch which fixes the problem partially by removing the false exit but it doesn't fix the issue completely because even with patch rpm touches packages which were already signed. Correct behaviour would be not to touch package which have already been correctly signed.
Created attachment 527292 [details] Patch which partially fixes the signing already signed packages problem. rpm-4.8.0 has backported broken change c0aad81e9b17afcbea4008485d354673495eb148 from rpm.org rpm git. That was supposed to fix #488953 but actually introduced even worse regression. When you try to sign packages in directory like: rpm --resign *.rpm rpm will exit with result code 0 when it finds first package which is correctly signed. This leaves very big possibility that you have dir of packages, only first ones being signed. rpm should actually only skip without modifications already singed packages. I attach patch which fixes the problem partially by removing the false exit but it doesn't fix the issue completely because even with patch rpm touches packages which were already signed. Correct behaviour would be not to touch package which have already been correctly signed.