[CentOS-devel] How does a 9-stream package move from Koji to released-to-mirrors?

Wed Jun 15 02:26:17 UTC 2022
Ian Wienand <iwienand at redhat.com>


We are waiting on a change made to libselinux [1] to hit the 9-stream
mirrors as described in [2].

It's rather unclear to me how this happens?  I have read [3] but
unfortunately I'm still not groking it.

I know this build has been committed to gitlib, and koji has picked it
up and built it [4].  It has tags

* c9s-build-side-477-stack-gate
* c9s-candidate
* c9s-pending

which [3] sort-of explains -- the package build has passed testing?

>From what I understand, it then goes into a compose visible from [5].
Not sure what "odcs" stands for, but these seem to be daily builds
(?-daily-centos-stream maybe?).

Then there is production/ which has timestamped directories currently:


Are these production composes weekly, daily, or perhaps ad-hoc
depending on somebody flipping a switch?

Something suggests to me that "latest-CentOS-Stream" should be ~= to
the mirror repos [6].  Is that right?

If I look in CentOS-STream-9-20220613.0 (latest-CentOS-stream,
currently), it indeed has libselinux-3.4-2 that we want.  However, if
I sort the mirror by date [7] nothing seems to have updated since
2022-06-06?  So, if I'm on the right track here -- what promotes the
"production" compose to the public mirrors?

Thanks for any insight


[1] https://gitlab.com/redhat/centos-stream/rpms/libselinux/-/commit/c68e490c94b21c6733eaa43aed9eba849b794a56
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2094683
[3] https://docs.centos.org/en-US/stream-contrib/quickstart/
[4] https://kojihub.stream.centos.org/koji/buildinfo?buildID=21551
[5] https://composes.stream.centos.org/
[6] http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/Packages/
[7] http://mirror.stream.centos.org/9-stream/BaseOS/x86_64/os/Packages/?C=M;O=D