On Thu, Nov 3, 2022, at 10:13, Greg Bailey wrote:

I've switched my CentOS Linux 8 workstation to CentOS Stream 8 quite some time ago, and haven't encountered too many issues doing so, but I'm curious as to why there haven't been any package updates that I can see in quite some time (since early October as far as I can see).

With the new stream process, my understanding is that for feature and bugfix development, the process is:

Git ---> CentOS Stream ---> RHEL (next minor version)

This is how things work for CentOS Stream 9. Code goes to https://gitlab.com/redhat/centos-stream/ first (though Important and Critical CVE fixes go to RHEL before being published)

But with security updates, it seems to be:

Git ---> RHEL (current minor version) ---> RHEL rebuilds (Rocky, Alma, etc)

I'm kind of surprised that my firefox and thunderbird builds still seem stuck at 91.13.0, when I've seen updates go by on the RHEL 8 channels with the newer firefox builds, etc.

What is the flow for security updates to make it into CentOS Stream package repositories?  Is there some documentation describing this that maybe I missed?  I don't remember seeing this on the CPE newsletter either.

CentOS Stream 8 is still accomplished "inside-out", though. This means code is pushed from a RHEL nightly build and then rebuilt for release in CentOS Stream 8. We're working on transitioning Stream 8 to the "proper" workflow that 9 uses.

In this particular case, I see that Firefox 102 made it into the 27-Oct compose: https://composes.centos.org/CentOS-Stream-8-20221027.n.0/

We'll be looking into why this isn't showing up on the mirrors.

Thanks, Greg

---

CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel

--Brian