Il giorno mar 8 apr 2025 alle ore 14:17 Fabian Arrotin <arrfab@centos.org> ha scritto:
On 07/04/2025 17:26, Neal Gompa wrote:
> On Mon, Apr 7, 2025 at 11:24 AM Troy Dawson via devel
> <devel@lists.centos.org> wrote:
>>
>> Looking beyond s390x, can we have them set by arch in some way.
>>
>> I'm thinking of the ISA SIG, we currently only have x86_64 packages built, and I didn't even think about our -release file being in other arches.
>> Plus, we're thinking of having SysV (is that the extension?) and wouldn't want others to think we're doing support for other arches.
>>
>> I guess we (ISA) could have our centos-release-isa rpm NOT be noarch, and specifically set the arch.
>>
>
> Do you mean RISC-V? But also you can just allow the repository to fail
> if it doesn't exist. Set "skip_if_unavailable=True" in the repo
> configs. The repositories already are set up to fetch archfully
> through repo variables.
>

Just as a summary, it seems we'd have two proposed approaches :

- Troy suggested modifying .spec for centos-release-<name> from
BuildArch: noarch to a list of supported architectures, that would (or
not) then be available under
https://mirror.stream.centos.org/SIGs/<stream-release>/extras/<arch>

- Neal proposed instead that can we keep it "noarch" but then .repo from
each SIG centos-release-<name> would need to be modified to ensure that
skip_if_unavailable=True would be added, otherwise it would still block
users from unsupported architecture if they install a
centos-release-<name> pkg that doesn't have pkgs / repository


What about creating the s390x repo always and leaving it empty if no package is built for that arch?
And let ExcludeArch deal with building on it or not.

 

In all the cases, that would need something to be done. For option 1 I
can change the build tag to add 's390x' (actually it only covers x85_64,
ppc64le and aarch64 - example for 9s :
https://cbs.centos.org/koji/taginfo?tagID=2556). But if I only do that,
the next time a pkg would be tagged, it would then import *all* existing
noarch in the s390x repository

What would be the best approach ? I'd like to hear from all SIGs as it's
about their packages in their repositories :)

--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

_______________________________________________
devel mailing list -- devel@lists.centos.org
To unsubscribe send an email to devel-leave@lists.centos.org


--

Sandro Bonazzola

MANAGER, ENGINEERING

Red Hat In-Vehicle Operating System

Red Hat EMEA

Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.