search for: passthejoe

...rnel has been behind RHEL for months, I begin to wonder, is it a symptom of something? What? Change of direction or simple lack of resources (recession and quiet quitting and all that jazz)? Is it time to switch to the old way (i.e. Rocky) again? > On 7. Jan 2023, at 20:05, Steven Rosenberg <passthejoe at gmail.com> wrote: > > If you want to follow CentOS Stream development, I have two websites that > grab CentOS-supplied XML and publish blog entries of updated packages > whenever that happens: > > https://centos.passthejoe.net/ > https://passthejoe.tilde.institute/cento...

If you want to follow CentOS Stream development, I have two websites that grab CentOS-supplied XML and publish blog entries of updated packages whenever that happens: https://centos.passthejoe.net/ https://passthejoe.tilde.institute/centos/ Both websites have the same content. Frustration with CentOS Stream 8 development and security -- especially the kernel -- drove me to create this site so progress in both distros (8 Stream and 9 Stream) would be easier to follow. Red Hat employees...

...ving the c8s process to use the same workflow as the c9s process. That will happen later this year. Right now, I only build what releases to git.centos.org for the c8s branch for the kernel. They are looking to get me a new kernel now. >> On 7. Jan 2023, at 20:05, Steven Rosenberg <passthejoe at gmail.com> wrote: >> >> If you want to follow CentOS Stream development, I have two websites that >> grab CentOS-supplied XML and publish blog entries of updated packages >> whenever that happens: >> >> https://centos.passthejoe.net/ >> https://passth...

Hi, Does anyone know what is happening with centos 8-Streams kernel? It has been behind RHEL for months now, RHEL8.7 has 4.18.0-425.3.1.el8 built in December and Streams has 4.18.0-408.el8 built all the way back in end October. Is there some policy somewhere that I missed that says that 9 will be now getting the focus or whatnot? thanks,

On Thu, Jan 12, 2023 at 2:02 PM Josh Boyer <jwboyer at redhat.com> wrote: Ultimately, the Red Hat teams are using modularity where they believe > it makes sense and using regular packaging to reduce complexity for > customers where it doesn't provide much benefit. > Thanks for the explanation. For those who want to know more, here is the documentation I used when I was trying