CentOS Stream 8 is transitioning to be ahead of RHEL 8 - Compose push to mirror operations affected
Hi Folks,
As many of you know, CentOS Stream 8 is currently produced using an "inside out" workflow, meaning RHEL builds happen first and then are reflected in CentOS Stream afterward. This is not the case with CentOS Stream 9 where builds are performed directly by maintainers at Red Hat from merge requests in gitlab.com.
The CentOS Stream team is busy working on a project to migrate CentOS Stream 8 to the gitlab.com/Stream-first workflow. This is an exciting step to reflect CentOS Stream's true purpose in both currently active releases.
One effect of this transition, though, is that we need to migrate from the old mbox buildsystem to the new Stream koji ( https://kojihub.stream.centos.org). To do this the team needs to pause regular compose and push-to-mirror jobs to avoid a split-brain situation with 2 separate systems. You may notice a lack of updates to the repos on the mirrors for a few more weeks while this transition is completed. The team's first priority is making sure that Red Hat maintainers take control over the c8s branches in https://gitlab.com/redhat/centos-stream/rpms (and builds in koji) and then the team will return to working on regular composes and push-to-mirror operations.
If you have any questions in the interim, please reach out to me.
Cheers!
-- Brian Stinson
On Sun, Feb 19, 2023 at 2:52 PM Brian Stinson bstinson@redhat.com wrote:
Hi Folks,
As many of you know, CentOS Stream 8 is currently produced using an "inside out" workflow, meaning RHEL builds happen first and then are reflected in CentOS Stream afterward. This is not the case with CentOS Stream 9 where builds are performed directly by maintainers at Red Hat from merge requests in gitlab.com.
The CentOS Stream team is busy working on a project to migrate CentOS Stream 8 to the gitlab.com/Stream-first workflow. This is an exciting step to reflect CentOS Stream's true purpose in both currently active releases.
One effect of this transition, though, is that we need to migrate from the old mbox buildsystem to the new Stream koji ( https://kojihub.stream.centos.org). To do this the team needs to pause regular compose and push-to-mirror jobs to avoid a split-brain situation with 2 separate systems. You may notice a lack of updates to the repos on the mirrors for a few more weeks while this transition is completed. The team's first priority is making sure that Red Hat maintainers take control over the c8s branches in https://gitlab.com/redhat/centos-stream/rpms (and builds in koji) and then the team will return to working on regular composes and push-to-mirror operations.
If you have any questions in the interim, please reach out to me.
Brian, can you help me understand how a package that is built in Koji makes its way to the CentOS repo? How can I tell when a package is going to be available for update, and is there a way to get Stream 8/9 packages sooner (and is that advisable)? Is there a way to follow a package that is similar to https://tracker.debian.org for CentOS?
On Tue, Feb 21, 2023 at 1:48 PM Steven Rosenberg passthejoe@gmail.com wrote:
On Sun, Feb 19, 2023 at 2:52 PM Brian Stinson bstinson@redhat.com wrote:
Hi Folks,
As many of you know, CentOS Stream 8 is currently produced using an "inside out" workflow, meaning RHEL builds happen first and then are reflected in CentOS Stream afterward. This is not the case with CentOS Stream 9 where builds are performed directly by maintainers at Red Hat from merge requests in gitlab.com.
The CentOS Stream team is busy working on a project to migrate CentOS Stream 8 to the gitlab.com/Stream-first workflow. This is an exciting step to reflect CentOS Stream's true purpose in both currently active releases.
One effect of this transition, though, is that we need to migrate from the old mbox buildsystem to the new Stream koji (https://kojihub.stream.centos.org). To do this the team needs to pause regular compose and push-to-mirror jobs to avoid a split-brain situation with 2 separate systems. You may notice a lack of updates to the repos on the mirrors for a few more weeks while this transition is completed. The team's first priority is making sure that Red Hat maintainers take control over the c8s branches in https://gitlab.com/redhat/centos-stream/rpms (and builds in koji) and then the team will return to working on regular composes and push-to-mirror operations.
If you have any questions in the interim, please reach out to me.
Brian, can you help me understand how a package that is built in Koji makes its way to the CentOS repo? How can I tell when a package is going to be available for update, and is there a way to get Stream 8/9 packages sooner (and is that advisable)? Is there a way to follow a package that is similar to https://tracker.debian.org for CentOS?
This might be a good start: https://blog.centos.org/2022/09/how-updates-work-in-centos/
I'll let Brian or others answer more fully. I think the short version is that users can download packages directly from the build system if they want, but those builds might not be fully vetted yet. We don't offer update metadata information either.
josh
On Tue, Feb 21, 2023 at 11:36 AM Josh Boyer jwboyer@redhat.com wrote:
This might be a good start: https://blog.centos.org/2022/09/how-updates-work-in-centos/
I'll let Brian or others answer more fully. I think the short version is that users can download packages directly from the build system if they want, but those builds might not be fully vetted yet. We don't offer update metadata information either.
josh
That's a very good post that explains a lot. I'm wondering if things have progressed in some way on Stream 9 vs. 8 relative to what's in that post.
Is the vetting process for packages to move from Koji to the repo similar to what happens in Fedora?
Hi Brian,
Does this update freeze affect security fixes as well? Will Stream 8 not receive any updates at all until the transition is completed, or will Critical updates still be released?
Cheers, Alex
On 2/19/23 23:52, Brian Stinson wrote:
Hi Folks,
As many of you know, CentOS Stream 8 is currently produced using an "inside out" workflow, meaning RHEL builds happen first and then are reflected in CentOS Stream afterward. This is not the case with CentOS Stream 9 where builds are performed directly by maintainers at Red Hat from merge requests in gitlab.com http://gitlab.com.
The CentOS Stream team is busy working on a project to migrate CentOS Stream 8 to the gitlab.com/Stream-first http://gitlab.com/Stream-first workflow. This is an exciting step to reflect CentOS Stream's true purpose in both currently active releases.
One effect of this transition, though, is that we need to migrate from the old mbox buildsystem to the new Stream koji (https://kojihub.stream.centos.org https://kojihub.stream.centos.org). To do this the team needs to pause regular compose and push-to-mirror jobs to avoid a split-brain situation with 2 separate systems. You may notice a lack of updates to the repos on the mirrors for a few more weeks while this transition is completed. The team's first priority is making sure that Red Hat maintainers take control over the c8s branches in https://gitlab.com/redhat/centos-stream/rpms https://gitlab.com/redhat/centos-stream/rpms (and builds in koji) and then the team will return to working on regular composes and push-to-mirror operations.
If you have any questions in the interim, please reach out to me.
Cheers!
-- Brian Stinson
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Feb 22, 2023 at 4:44 AM Alex Iribarren alex.m.lists3@gmail.com wrote:
Hi Brian,
Does this update freeze affect security fixes as well? Will Stream 8 not receive any updates at all until the transition is completed, or will Critical updates still be released?
That is correct. The convergence of workflows is a high priority but relatively short duration item so builds will begin again once it is complete. As a reminder, CentOS overall has no CVE fix SLAs or guarantees, and Critical CVE fixes go directly to RHEL first.
josh
On 2/19/23 23:52, Brian Stinson wrote:
Hi Folks,
As many of you know, CentOS Stream 8 is currently produced using an "inside out" workflow, meaning RHEL builds happen first and then are reflected in CentOS Stream afterward. This is not the case with CentOS Stream 9 where builds are performed directly by maintainers at Red Hat from merge requests in gitlab.com http://gitlab.com.
The CentOS Stream team is busy working on a project to migrate CentOS Stream 8 to the gitlab.com/Stream-first http://gitlab.com/Stream-first workflow. This is an exciting step to reflect CentOS Stream's true purpose in both currently active releases.
One effect of this transition, though, is that we need to migrate from the old mbox buildsystem to the new Stream koji (https://kojihub.stream.centos.org https://kojihub.stream.centos.org). To do this the team needs to pause regular compose and push-to-mirror jobs to avoid a split-brain situation with 2 separate systems. You may notice a lack of updates to the repos on the mirrors for a few more weeks while this transition is completed. The team's first priority is making sure that Red Hat maintainers take control over the c8s branches in https://gitlab.com/redhat/centos-stream/rpms https://gitlab.com/redhat/centos-stream/rpms (and builds in koji) and then the team will return to working on regular composes and push-to-mirror operations.
If you have any questions in the interim, please reach out to me.
Cheers!
-- Brian Stinson
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Alex Iribarren -
Brian Stinson -
Josh Boyer -
Steven Rosenberg