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.
This originates from splitting the cockpit-ostree package sources out into a new cockpit-ostree project/dist-git. There should be no visible change for the cockpi-ostree rpm subpackage.
So this is most likely a no-op.
Are the packages that make up RHEL Atomic even managed in comps? I don't see anything related in https://code.engineering.redhat.com/gerrit/gitweb?p=comps.git;a=tree
But regardless of where it is maintained, the binary package has existed before and has been on Atomic for a long time, thus there shouldn't be any changes necessary.
So this can likely just be closed (it blocks the Maitai process and this needs to finish soon now).
(In reply to Martin Pitt from comment #3)
> Are the packages that make up RHEL Atomic even managed in comps? I don't see
> anything related in
> https://code.engineering.redhat.com/gerrit/gitweb?p=comps.git;a=tree
>
> But regardless of where it is maintained, the binary package has existed
> before and has been on Atomic for a long time, thus there shouldn't be any
> changes necessary.
>
> So this can likely just be closed (it blocks the Maitai process and this
> needs to finish soon now).
Atomic Host doesn't use comps.xml, but perhaps it should. FYI it uses the pungi package filters to whitelist/blacklist things.
Moving to close this out, as to unblock maitai.