CentOS's build system and the Community Build Service (CBS) — where the SIG packages get built — use incarnations of Fedora's Koji. (I presume it comes from Fedora anyway, but I could be wrong.) E.g. Stream is on https://kojihub.stream.centos.org/koji and the SIG packages get built on CBS at https://cbs.centos.org/koji/. There was a different koji instance for C8 before Stream8 and C7 and earlier, which name escapes me.
The CLIs that packagers use are called fedpkg and koji for Fedora, cbs for CBS, and I'm not sure what the CLI is for Stream, I don't use that, I don't work on Stream. There are a lot of other pieces too, e.g. bodhi is for update management I think in Fedora, and account management. CentOS had their own account management for a while then later switched to Fedora's FAS. CBS doesn't use bodhi, updates are managed by the packagers. There are other backend pieces that sign the RPMs and build the repos. I honestly don't even know what all the pieces are. There are people on #centos-devel (on Libera.chat) like arrfab, bstinson, hughesjr, and carlwgeorge to name a few, who know all the details. You should make friends with them. ;-) But you don't really need all that just to build packages. You could just set up a Stream8 box and do all your builds, signing, and repo creation on it. Which is what is/was done for gluster's Debian packages. For bonus points set it up as a container and use k8s or ansible to fire up an image and do the builds when you need them. On Tue, Aug 16, 2022 at 6:43 PM Strahil Nikolov <hunter86...@yahoo.com> wrote: > Hey Kaleb, > thanks for your reply. I was affraid of that. > > How can I get more info about the build process ? Maybe we can replicate > the setup as a Rocky SIG . > > Best Regards, > Strahil Nikolov > > On Mon, Aug 15, 2022 at 15:15, Kaleb Keithley > <kkeit...@redhat.com> wrote: > > On Sun, Aug 14, 2022 at 8:31 AM Strahil Nikolov <hunter86...@yahoo.com> > wrote: > > > Yet, when I asked the CentOS Storage SIG about the situation after the > CentOS Stream goes end of life -> there was no definitive answer. > > > I'm not sure asking the Storage SIG is the right thing to do. The SIGs > are subject to whatever CentOS decides. > > E.g. if you look at C6 vs C7 on http://mirror.centos.org/centos/, the SIG > repos are there (obviously) for C7, but *everything* is gone for C6 (and > earlier) including all the SIG repos. (But it is all achieved on > https://vault.centos.org/ so it's not truly gone.) > > If everything in Stream8 and everything related to Stream8 gets removed at > Stream8's EOL by CentOS, that's nothing to do with the SIGs. > > I kinda suspect that some Stream8 stuff will stick around for a little > while, but we — i.e. the SIGs — are not part of that decision process. > > And I pretty much guarantee that all the build infra around Stream8 will > get torn down pretty quickly and there won't be any further updates to any > of the software. > > -- > > Kaleb > > -- Kaleb
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Glusterfirstname.lastname@example.org https://lists.gluster.org/mailman/listinfo/gluster-users