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.