I’m submitting src.rpms to build against several chroots. For discussion, lets consider epel-9-aarch64 and epel-9-x86_64. When I build a binary rpm, I expect those results to be seen in different repositories. But, if I submit a noarch rpm – it appears I have to build those separately for each arch (chroot). Is that expected? I would have hoped that the noarch rpms would be accessible across the board. I’m using a dnf repoquery –force-arch option to ‘see’ what is in my copr repo (wish there was a way to view those pkgs via the copr web interface). When I force-arch to aarch64 I only see ‘noarch’ pkgs that were submitted to the epel-9-aarch chroot. I suppose that is understandable – but I thought there was effectively ‘one repo’ per project (except for the necessary arch distinctions)
I end up building my noarch in each arch I support.
I’m not aware of any noarch repos in copr.
That is expected.
We have an old RFE for building noarch RPMs just once but nobody implemented it yet.
There might be in the future. We are currently migrating our build results to Pulp
and independently on that effort, the Pulp team is working on a web interface for inspecting RPM and other repositories.