For the other 3 architectures its the same:
[root@7a08b3ab8faf /]# dnf repoquery --repofrompath tmp,https://mirror.stream.centos.org/SIGs/9-stream/extras/x86_64/extras-common --disablerepo=* --enablerepo=tmp > x86_64.txt Updating and loading repositories: tmp 100% | 44.7 KiB/s | 17.2 KiB | 00m00s Repositories loaded. [root@7a08b3ab8faf /]# dnf repoquery --repofrompath tmp,https://mirror.stream.centos.org/SIGs/9-stream/extras/aarch64/extras-common --disablerepo=* --enablerepo=tmp > aarch64.txt Updating and loading repositories: tmp 100% | 38.7 KiB/s | 17.2 KiB | 00m00s Repositories loaded. [root@7a08b3ab8faf /]# dnf repoquery --repofrompath tmp,https://mirror.stream.centos.org/SIGs/9-stream/extras/ppc64le/extras-common --disablerepo=* --enablerepo=tmp > ppc64le.txt Updating and loading repositories: tmp 100% | 29.2 KiB/s | 17.2 KiB | 00m01s Repositories loaded. [root@7a08b3ab8faf /]# dnf repoquery --repofrompath tmp,https://mirror.stream.centos.org/SIGs/9-stream/extras/s390x/extras-common --disablerepo=* --enablerepo=tmp > s390x.txt Updating and loading repositories: tmp 100% | 6.9 KiB/s | 3.1 KiB | 00m00s Repositories loaded. [root@7a08b3ab8faf /]# md5sum *.txt 17261a165dd24cea76bf58c05636e8b5 aarch64.txt 17261a165dd24cea76bf58c05636e8b5 ppc64le.txt d41d8cd98f00b204e9800998ecf8427e s390x.txt 17261a165dd24cea76bf58c05636e8b5 x86_64.txt
but for s390x it's empty:
[root@7a08b3ab8faf /]# cat s390x.txt | wc -l 0
yes, https://mirror.stream.centos.org/SIGs/9-stream/extras/s390x/extras-common/ and same for Stream 10 , is actually just empty because for a long time, there was no s390x builder for cbs.centos.org and so SIG content
So an empty repository was created. Now we have s390x arch supported but only a very few SIGs opted-in and just shipping .noarch for all SIGs would be possible but then next step would be failing for people on s390x (probably not a lot though) trying to install a centos-release-$<sig> that doesn't provide any repo for s390x
centos-release-$<sig>
AFAIK, only the following SIGs are building now for s390x :
Can you describe the current issue you're facing ? Ideally we'd use this ticket as a wider discussion on the centos-devel list so that people can come with ideas too
Metadata Update from @arrfab: - Issue assigned to arrfab - Issue tagged with: cbs, feature-request, investigation, need-more-info
Hi @arrfab Please see the comment [1] for more context on the issue. Basically, we'd like to keep $basearch instead of having to set x86_64 for sake of consistency.
$basearch
x86_64
[1] https://github.com/dustymabe/os/blob/9b587eba62755cb1adb74505b0424dcdb1a11026/c9s.repo#L39-L41
FTR https://lists.centos.org/hyperkitty/list/devel@lists.centos.org/thread/ITHOTZT3GEEIGLRA4CTW6QI67MYGWUFM/ the centos-devel ML thread where the discussion is taking place
it seems there is no momentum/traction on centos-devel list and no real consensus ... What are your opinions about this ? I'd still be tempted to just add s390x and then make it a SIGs problem and so having all to just stop building as noarch but rather make it arch dependent ...
noarch
I'm ok with either solution I guess.
Just to let you know that from today, s390x was added as architecture for the extras9s and extras10s , so centos-release* pkgs noarch packages will be also pushed there automatically. I updated the thread on devel list to let SIGs know that if they want to switch from noarch to arch dependent for their -release pkgs, they can
Closing this request
Metadata Update from @arrfab: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.