Hi,
Long awaited feature request is now implemented on https://cbs.centos.org : you can now start requesting 9s tags to build against/for CentOS Stream 9 !
I already created some tags/targets for SIGs that already requested it some time ago through our dedicated infra tracker (reminder: https://pagure.io/centos-infra/issues)
Worth knowing that the following repositories are enabled by default for all newly created 9s tags: - BaseOS - AppStream - CRB
What's possible to add ? I know that for 8/8s some SIGs (like Cloud SIG for openstack) rely on other repositories, like HighAvailability , or others. Feel free to ask such repositories to be added to your build tags.
It's also possible to build against CentOS Stream 9 buildroots if the pushed repositories don't include all -devel / runtime packages that you need at buildtime. For that, consider also asking for it if/when needed.
Important ! Due to the way Stream 9 will be delivered (more news on that later, probably through Brian and/or Carl), I have locked all -release tags for 9s.
What does that mean ? That you can build pkgs, and also tag to -testing (that will go out as usual to buildlogs.centos.org) but not to -release (even if tag is created already).
Once we'll have figured out how to properly sign+push SIG content out, we'll announce the plan and also unlock the -release SIG tags
Stay tuned for more information about that soon.
Kind Regards,
On 03/09/2021 14:56, Fabian Arrotin wrote:
Hi,
Long awaited feature request is now implemented on https://cbs.centos.org : you can now start requesting 9s tags to build against/for CentOS Stream 9 !
I already created some tags/targets for SIGs that already requested it some time ago through our dedicated infra tracker (reminder: https://pagure.io/centos-infra/issues)
Worth knowing that the following repositories are enabled by default for all newly created 9s tags:
- BaseOS
- AppStream
- CRB
What's possible to add ? I know that for 8/8s some SIGs (like Cloud SIG for openstack) rely on other repositories, like HighAvailability , or others. Feel free to ask such repositories to be added to your build tags.
It's also possible to build against CentOS Stream 9 buildroots if the pushed repositories don't include all -devel / runtime packages that you need at buildtime. For that, consider also asking for it if/when needed.
Important ! Due to the way Stream 9 will be delivered (more news on that later, probably through Brian and/or Carl), I have locked all -release tags for 9s.
What does that mean ? That you can build pkgs, and also tag to -testing (that will go out as usual to buildlogs.centos.org) but not to -release (even if tag is created already).
Once we'll have figured out how to properly sign+push SIG content out, we'll announce the plan and also unlock the -release SIG tags
Stay tuned for more information about that soon.
Kind Regards,
It wasn't that long before some SIGs started to test building on cbs.centos.org (I like the Momentum !) .. and so that first issue was found : CentOS Stream 9 ppc64le requires IBM Power 9, which we don't have for builders for cbs.centos.org .. :
Error in <unknown> scriptlet in rpm package glibc-common Fatal glibc error: CPU lacks ISA 3.00 support (POWER9 or later required) warning: %transfiletriggerin(glib2-2.68.4-1.el9.ppc64le) scriptlet failed, exit status 127
So that means that for now, we have to decide on what to do : SIGs can request to build only for x86_64/aarch64 and let ppc64le aside and we can try to see if there is a way to find an IBM Power 9 machine that we can use for SIGs/cbs
Il giorno ven 3 set 2021 alle ore 15:40 Fabian Arrotin arrfab@centos.org ha scritto:
It wasn't that long before some SIGs started to test building on cbs.centos.org (I like the Momentum !) .. and so that first issue was found : CentOS Stream 9 ppc64le requires IBM Power 9, which we don't have for builders for cbs.centos.org .. :
Error in <unknown> scriptlet in rpm package glibc-common Fatal glibc error: CPU lacks ISA 3.00 support (POWER9 or later required) warning: %transfiletriggerin(glib2-2.68.4-1.el9.ppc64le) scriptlet failed, exit status 127
So that means that for now, we have to decide on what to do : SIGs can request to build only for x86_64/aarch64 and let ppc64le aside and we can try to see if there is a way to find an IBM Power 9 machine that we can use for SIGs/cbs
For oVirt we can start with x86_64 and aarch64. I'll see if we can help with this.
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 03/09/2021 15:40, Fabian Arrotin wrote:
On 03/09/2021 14:56, Fabian Arrotin wrote:
Hi,
<snip>
It wasn't that long before some SIGs started to test building on cbs.centos.org (I like the Momentum !) .. and so that first issue was found : CentOS Stream 9 ppc64le requires IBM Power 9, which we don't have for builders for cbs.centos.org .. :
<snip>
We were finally able to have at least one Power9 VM available and thanks to a specific kojihub policy, we can redirect Stream 9 builds on specific hosts, so we tested that it worked for a gluster build : https://cbs.centos.org/koji/buildinfo?buildID=34013
That's a workaround that at least unblocks all SIGs willing to build for both x86_64, aarch64 and ppc64le ...
And yes, even if CentOS Stream 9 itself will be built and available for s390x architecture, that's not possible to have such arch supported by cbs infra.
On Fri, 2021-09-03 at 14:56 +0200, Fabian Arrotin wrote:
Hi,
Long awaited feature request is now implemented on https://cbs.centos.org%C2%A0: you can now start requesting 9s tags to build against/for CentOS Stream 9 !
I already created some tags/targets for SIGs that already requested it some time ago through our dedicated infra tracker (reminder: https://pagure.io/centos-infra/issues)
Thank you!
I just tried this out with kpatch, and it seems to work fine: https://cbs.centos.org/koji/taskinfo?taskID=2530362
One caveat to be aware of: cbs expects repos to be in the old rpmbuild layout (i.e. with SOURCES/SPECS, like on c8s), while the centpkg and centpkg-sig tools seem to expect a new-style layout. This is what I've pushed for kpatch so far for reference: https://git.centos.org/rpms/kpatch/tree/c9s-sig-hyperscale
Cheers Davide
On 03/09/2021 16:40, Davide Cavalca via CentOS-devel wrote:
On Fri, 2021-09-03 at 14:56 +0200, Fabian Arrotin wrote:
Hi,
Long awaited feature request is now implemented on https://cbs.centos.org%C2%A0: you can now start requesting 9s tags to build against/for CentOS Stream 9 !
I already created some tags/targets for SIGs that already requested it some time ago through our dedicated infra tracker (reminder: https://pagure.io/centos-infra/issues)
Thank you!
I just tried this out with kpatch, and it seems to work fine: https://cbs.centos.org/koji/taskinfo?taskID=2530362
One caveat to be aware of: cbs expects repos to be in the old rpmbuild layout (i.e. with SOURCES/SPECS, like on c8s), while the centpkg and centpkg-sig tools seem to expect a new-style layout. This is what I've pushed for kpatch so far for reference: https://git.centos.org/rpms/kpatch/tree/c9s-sig-hyperscale
Cheers Davide
Hi Davide,
Yes, it's still git.centos.org and cbs.centos.org so nothing changed : the same get_sources.sh is used to rebuild src.rpm from git and so expect the same layout ("rpmbuild" style) .. Thanks for having clarified that on the -devel list, in case it wasn't obvious for all SIGs members :) (as yes, upstream Stream 9 repositories on gitlab are in the "flat" layout)
Hi Fabian,
On Fri, Sep 03, 2021 at 04:43:54PM +0200, Fabian Arrotin wrote:
On 03/09/2021 16:40, Davide Cavalca via CentOS-devel wrote:
One caveat to be aware of: cbs expects repos to be in the old rpmbuild layout (i.e. with SOURCES/SPECS, like on c8s), while the centpkg and centpkg-sig tools seem to expect a new-style layout. This is what I've pushed for kpatch so far for reference: https://git.centos.org/rpms/kpatch/tree/c9s-sig-hyperscale
Cheers Davide
Hi Davide,
Yes, it's still git.centos.org and cbs.centos.org so nothing changed : the same get_sources.sh is used to rebuild src.rpm from git and so expect the same layout ("rpmbuild" style) .. Thanks for having clarified that on the -devel list, in case it wasn't obvious for all SIGs members :) (as yes, upstream Stream 9 repositories on gitlab are in the "flat" layout)
How feasible would it be to support the flat layout at least for SIG branches targeting c9s, but ideally also supporting it for c8s too?
It would make it much easier for SIGs to build packages based off Fedora or Stream 9 and keeping them in sync with the original repos.
Happy to lend a hand if this is something that is desirable and we just need someone to actually do it.
Thanks,
On Tue, Nov 30, 2021 at 5:22 PM Michel Alexandre Salim michel@michel-slm.name wrote:
Hi Fabian,
On Fri, Sep 03, 2021 at 04:43:54PM +0200, Fabian Arrotin wrote:
On 03/09/2021 16:40, Davide Cavalca via CentOS-devel wrote:
One caveat to be aware of: cbs expects repos to be in the old rpmbuild layout (i.e. with SOURCES/SPECS, like on c8s), while the centpkg and centpkg-sig tools seem to expect a new-style layout. This is what I've pushed for kpatch so far for reference: https://git.centos.org/rpms/kpatch/tree/c9s-sig-hyperscale
Cheers Davide
Hi Davide,
Yes, it's still git.centos.org and cbs.centos.org so nothing changed : the same get_sources.sh is used to rebuild src.rpm from git and so expect the same layout ("rpmbuild" style) .. Thanks for having clarified that on the -devel list, in case it wasn't obvious for all SIGs members :) (as yes, upstream Stream 9 repositories on gitlab are in the "flat" layout)
How feasible would it be to support the flat layout at least for SIG branches targeting c9s, but ideally also supporting it for c8s too?
It would make it much easier for SIGs to build packages based off Fedora or Stream 9 and keeping them in sync with the original repos.
Happy to lend a hand if this is something that is desirable and we just need someone to actually do it.
Last I talked to Brian about this, it just needs someone to finish implementing the logic for it.
On 03/09/2021 13:56, Fabian Arrotin wrote:
Hi,
Long awaited feature request is now implemented on https://cbs.centos.org : you can now start requesting 9s tags to build against/for CentOS Stream 9 !
I already created some tags/targets for SIGs that already requested it some time ago through our dedicated infra tracker (reminder: https://pagure.io/centos-infra/issues)
Worth knowing that the following repositories are enabled by default for all newly created 9s tags:
- BaseOS
- AppStream
- CRB
What is 'CRB' repo about? Also other new (to me at least) repos in 9er? ps. I wish 'dnf repoinfo' had answers to such questions so there will be no need to bother people. many thanks, L.
What's possible to add ? I know that for 8/8s some SIGs (like Cloud SIG for openstack) rely on other repositories, like HighAvailability , or others. Feel free to ask such repositories to be added to your build tags.
It's also possible to build against CentOS Stream 9 buildroots if the pushed repositories don't include all -devel / runtime packages that you need at buildtime. For that, consider also asking for it if/when needed.
Important ! Due to the way Stream 9 will be delivered (more news on that later, probably through Brian and/or Carl), I have locked all -release tags for 9s.
What does that mean ? That you can build pkgs, and also tag to -testing (that will go out as usual to buildlogs.centos.org) but not to -release (even if tag is created already).
Once we'll have figured out how to properly sign+push SIG content out, we'll announce the plan and also unlock the -release SIG tags
Stay tuned for more information about that soon.
Kind Regards,
On Mon, Oct 25, 2021 at 5:15 PM lejeczek via CentOS-devel centos-devel@centos.org wrote:
On 03/09/2021 13:56, Fabian Arrotin wrote:
Hi,
Long awaited feature request is now implemented on https://cbs.centos.org : you can now start requesting 9s tags to build against/for CentOS Stream 9 !
I already created some tags/targets for SIGs that already requested it some time ago through our dedicated infra tracker (reminder: https://pagure.io/centos-infra/issues)
Worth knowing that the following repositories are enabled by default for all newly created 9s tags:
- BaseOS
- AppStream
- CRB
What is 'CRB' repo about? Also other new (to me at least) repos in 9er? ps. I wish 'dnf repoinfo' had answers to such questions so there will be no need to bother people.
CRB is the replacement for the PowerTools repo. It's the CodeReady Builder repository.
On 25/10/2021 23:15, lejeczek via CentOS-devel wrote:
On 03/09/2021 13:56, Fabian Arrotin wrote:
Hi,
Long awaited feature request is now implemented on https://cbs.centos.org : you can now start requesting 9s tags to build against/for CentOS Stream 9 !
I already created some tags/targets for SIGs that already requested it some time ago through our dedicated infra tracker (reminder: https://pagure.io/centos-infra/issues)
Worth knowing that the following repositories are enabled by default for all newly created 9s tags:
- BaseOS
- AppStream
- CRB
What is 'CRB' repo about? Also other new (to me at least) repos in 9er? ps. I wish 'dnf repoinfo' had answers to such questions so there will be no need to bother people. many thanks, L.
These are all the known RHEL repositories, and CRB = CodeReady Builder. see following linkhttps://developers.redhat.com/blog/2018/11/15/introducing-codeready-linux-bu...
(That was called Powertools in Stream 8 but back to same name as in RHEL for Stream 9)
On 03/09/2021 14:56, Fabian Arrotin wrote:
Hi,
Long awaited feature request is now implemented on https://cbs.centos.org : you can now start requesting 9s tags to build against/for CentOS Stream 9 !
I already created some tags/targets for SIGs that already requested it some time ago through our dedicated infra tracker (reminder: https://pagure.io/centos-infra/issues)
Worth knowing that the following repositories are enabled by default for all newly created 9s tags:
- BaseOS
- AppStream
- CRB
What's possible to add ? I know that for 8/8s some SIGs (like Cloud SIG for openstack) rely on other repositories, like HighAvailability , or others. Feel free to ask such repositories to be added to your build tags.
It's also possible to build against CentOS Stream 9 buildroots if the pushed repositories don't include all -devel / runtime packages that you need at buildtime. For that, consider also asking for it if/when needed.
Important ! Due to the way Stream 9 will be delivered (more news on that later, probably through Brian and/or Carl), I have locked all -release tags for 9s.
What does that mean ? That you can build pkgs, and also tag to -testing (that will go out as usual to buildlogs.centos.org) but not to -release (even if tag is created already).
Once we'll have figured out how to properly sign+push SIG content out, we'll announce the plan and also unlock the -release SIG tags
Stay tuned for more information about that soon.
Hey SIG members !
Just to let you know that mirrormanager is in place so we have unlocked the -release tags for stream 9, so if you tag to -release, that would push your repo content to http://mirror.stream.centos.org/SIGs/9-stream/
We'll do a follow-up next week about the centos-release-* packages , moving to their own new repo/sig so that it would be built and pushed directly from cbs, but that needs a modification first in stream 9 distro content itself (basically the .repo and the dedicated gpg public key that will be used to sign these release pkgs)
Once you'll have content available, mirrormanager should be able (normally but we can then ask Adrian Reber to investigate that) to detect new repositories/repodata under /SIGs/9-stream and so start producing valid metalink for these repositories.
Based on information I got from Adrian, the logic/pattern to use to call for metalink would be :
repo=centos-<sig-name>-sig-<project>-<release>-9-stream&arch=<basearch>
So if we have a look at infra sig, using infra9s-infra-common-release as cbs/koji tag, it's this path on mirror.stream.centos.org: http://mirror.stream.centos.org/SIGs/9-stream/infra/x86_64/infra-common/
and metalink being : curl 'https://mirrors.centos.org/metalink?repo=centos-infra-sig-infra-common-9-str...'
variant for source and debug repo=centos-infra-sig-infra-common-debug-9-stream&arch=x86_64 repo=centos-infra-sig-infra-common-source-9-stream&arch=source
Once we'll have more content we'll be able to validate that but main announce here is that all -release tags for stream 9 are now unlocked
-
Davide Cavalca -
Fabian Arrotin -
lejeczek -
Michel Alexandre Salim -
Neal Gompa -
Sandro Bonazzola