Hi,
Since s390x was only recently added and most SIGs don't support s390x, we need a way to allow these SIGs to configure their release packages to not be published for s390x. It would be even better if the SIGs could set their release packages to be published for s390x, i.e., opt-in instead of opt-out.
On 05/04/2025 15.16, Fabian Arrotin wrote:
Hi,
Dusty created a ticket on infra tracker about empty s390x repo for extras-common : https://pagure.io/centos-infra/issue/1635
For visibility/awareness I'd like to discuss that here and then work on ticket eventually, as it would involve other SIGs.
For a long time, we had no s390x arch support in CBS but it was finally available end of 2024 (https://lists.centos.org/hyperkitty/list/ devel@lists.centos.org/thread/YW24YOCOSVFMZ5FLB3CMX2UXSUOFTVDF/)
So, now the interesting question : what to do about s390x ? It's easy to just add it to the extras-common build tag (https:// cbs.centos.org/koji/taginfo?tagID=2914), and it would start pushing centos-release* noarch pkgs out , and so available for s390x users (are there a lot of these ? )
But while it would "solve" the issue mentioned by Dusty above, it would be giving impression that there are SIG content s(like ceph/gluster/ else, so content built by SIGs) available for s390x, while only NFV/ Infra (for our own needs)/OKD started to build for s390x.
As a reminder, that extras-common repository is only used for SIGs to distribute their -release packages (containing .repo files and gpg pub key) so that it can be directly installed from a centos stream release (that's the only repo that is available by default, coming from CBS - community and so outside of stream repositories like BaseOS/AppStream/ CRB/etc)
I'd like to have your opinion/thoughs/feedback about this .
devel mailing list -- devel@lists.centos.org To unsubscribe send an email to devel-leave@lists.centos.org