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.
Description of problem:
The EPEL 9 package suffers from the same issues that the Fedora package had.
The Fedora Package was fixed.
Version-Release number of selected component (if applicable):
aqute-bnd-5.2.0-5.el9
(The version in the EPEL 9 buildroot in Fedora Koji)
How reproducible:
Try rebuilding bouncycastle in the EPEL 9 koji.
https://koji.fedoraproject.org/koji/taskinfo?taskID=80123138
Steps to Reproduce:
1. fedpkg clone bouncycastle
2. cd bouncycastle
3. fedpkg --release epel9 build --scratch
Actual results:
Failure
Expected results:
Success
Additional info:
See bug #1985566 for the same issue in Fedora.
This is the commit that fixed this issue in Fedora:
https://src.fedoraproject.org/rpms/aqute-bnd/c/acbb11e36d743e08e832138d01675dd0ae17c087?branch=rawhide
Confirmed - biz.aQute.bnd.jar is empty, it does not contain any .class files.
Scope of the change:
Backport fix from Fedora: https://src.fedoraproject.org/rpms/aqute-bnd/pull-request/9
New test are required:
- implement smoke test to check that basic usage of "bnd" command works (eg. "bnd print $jar")
- implement regression test to check that every JAR file in the package contains at least one class file
Actions to pre-verify the bug:
- check that gating test were implemented
- check that all gating tests (existing and new) passed
Pre-verification:
1) Checked commits in CentOS branch, smoke test as well as regression tests were implemented and test what is required: usage of `bnd` and the presence of `.class` files inside `.jar` archives.
2) All automated gating tests passed, including the newly added ones.
The results of MBI manual gating test were not yet reported in OSCI dashboard. I executed the manual test myself against the latest CentOS compose packages as of 22. 12. 2021 + the newest commit in aqute-bnd branch and the test passed but I don't have a place to share the result persistently.
Depending on the manual gating test, the pre-verification step is considered successful.
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 (new packages: aqute-bnd), 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-2022:4303