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:
Specfile of scap-workbench is collectionized, but in the way that it fails if environment is collection-aware. Reason is Requires and BuildRequires fields point to collectionized version of openscap-utils package, but openscap component is NOT collectionized. Thus inevitable failure occurs.
Version-Release number of selected component (if applicable):
scap-workbench-1.1.1-1.el6
How reproducible:
reliably
Steps to Reproduce:
1. see openscap spec file
2. see scap-workbench, Requires and BuildRequires field
Actual results:
Package openscap does not use scl_ macros.
Package scap-workbench has Requirements utilizing %{?scl_prefix}
Expected results:
scap-workbench does not requires collectionized openscap
Additional information:
There is no issue with scap-workbench itself being collectionized.
Description of problem: Specfile of scap-workbench is collectionized, but in the way that it fails if environment is collection-aware. Reason is Requires and BuildRequires fields point to collectionized version of openscap-utils package, but openscap component is NOT collectionized. Thus inevitable failure occurs. Version-Release number of selected component (if applicable): scap-workbench-1.1.1-1.el6 How reproducible: reliably Steps to Reproduce: 1. see openscap spec file 2. see scap-workbench, Requires and BuildRequires field Actual results: Package openscap does not use scl_ macros. Package scap-workbench has Requirements utilizing %{?scl_prefix} Expected results: scap-workbench does not requires collectionized openscap Additional information: There is no issue with scap-workbench itself being collectionized.