This is resulting in build failures for epel10 packages (https://pagure.io/releng/issue/12305) and no doubt other issues too.
per definition for Stream (see https://wiki.centos.org/ReportBugs.html), can you instead create a Jira ticket on issues.redhat.com ? That's the tracker that CentOS Stream team is using (this tracker is about centos infra, and we don't manage stream content)
Metadata Update from @arrfab: - Issue close_status updated to: Wrong tracker - Issue status updated to: Closed (was: Open)
The packages are there, but missing from primary.xml. Current of CentOS-Stream-10-20240903.0 compose is https://mirror.stream.centos.org/10-stream/BaseOS/x86_64/os/repodata/12892a4b1a9c46b2b8fda44f7f88bdac42e9275a6e4b47ae4139cd0285e7451b-primary.xml.gz which indeed lists only shim packages, while the previous one https://mirror.stream.centos.org/10-stream/BaseOS/x86_64/os/repodata/dbedd16f568573ca066246419abcdf059534329c1eb80d857e6d9713a27501a3-primary.xml.gz is all right.
Did merging secureboot-signed packages and normal packages fail?
@arrfab, what component in Jira is suitable for bugs in compose process?
I used "distribution" and raised this: https://issues.redhat.com/browse/RHEL-57074
I'd be tempted to answer that it should be a different project completely (the CS / CentOS Stream pipeline in Jira) but the official statement we received in the past is the one on that archived wiki page :
The Component field corresponds to the source package name that you'd like to report a bug against. If you are reporting an issue against the whole distribution itself, or if you're otherwise unclear what the component should be please choose 'distribution'.
PS: not supposed to, but I also internally pinged someone who can eventually have a look at that
I see that @pghmcfc was faster than me to type "enter" to submit the answer :)
The Jira issue is private, at least to me.
I don't see a way to change the visibility of the JIRA ticket (don't even know if it's possible), sorry.
I made that Jira ticket public. There are no private data and it was turned private by a bot. I cannot guarantee the bot won't come again.
The ticket was changed to CentOS STream Pipeline https://issues.redhat.com/browse/CS-2510
The problem has been found and fixed. We have created a new compose and it is on it's way to the mirrors (after we verified that the fix worked). Mirrors take a while to propogate, so it will take a few hours.
This has propogated to enough mirrors, and EPEL10 has now been fixed, that I am going to consider this done. But this isn't my ticket, so I can't close it.
Local and koji builds are all working for me now - thanks. Ticket was actually closed 6 hours ago.
Log in to comment on this ticket.