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 development model of scap-security-guide project (happening at https://github.com/OpenSCAP/scap-security-guide) is pretty agile / prompt (in the sense the available SCAP content is evolving pretty quickly. For the purposes of statistics, based on previous experience, it's about 70 changes per release). The current version of scap-security-guide package in Red Hat Enterprise Linux 6 is based on upstream 0.1.18 version.
This bug is to track request of scap-security-guide RPM rebase to more recent (current upstream version) in upcoming releases of Red Hat Enterprise Linux 6.
(In reply to Shawn Wells from comment #4)
> To prepare for a RHEL 6.7 rebase, when should upstream have their code
> freeze?
>
> Thanks!
> Shawn
From SSG upstream PoV there are two main features, that should go into future / next SSG releases:
* USGCB kickstart support for Red Hat Enterprise Linux 6, and
* JBossEAP 5 content support.
Given the USGCB kickstart support is ~month away from completion, let's consider it will be implemented by the end of this year (time reserve due to end year holidays). Counting ~1,5 months for the second feature, we are in the middle of February. So let's round the date(s) as follows:
* 0.1.20 upstream release by end of this year,
* 0.1.21 at 20-th February of 2015 (the date to be easily memorable).
The RHEL 6.7 beta Package scap-security-guide-0.1.21-2.el6.noarch.rpm still has a dependency on openscap-utils, but it should depend on openscap-scanner as RHEL 6.7 beta now has a separate openscap-scanner package. Dependending on openscap-utils leads to installation of eg. rpm-build, rpmdevtools, gdb.
(In reply to Stephan Dühr from comment #25)
> The RHEL 6.7 beta Package scap-security-guide-0.1.21-2.el6.noarch.rpm still
> has a dependency on openscap-utils, but it should depend on openscap-scanner
> as RHEL 6.7 beta now has a separate openscap-scanner package. Dependending
> on openscap-utils leads to installation of eg. rpm-build, rpmdevtools, gdb.
Thank you for your report, Stephan. I have filed:
https://bugzilla.redhat.com/show_bug.cgi?id=1243396
bug to track the request scap-security-guide RPM instead of openscap-utils to (R / BR) depend the lightweight openscap-scanner package.
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, 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://rhn.redhat.com/errata/RHBA-2015-1334.html