Description of problem: `ExclusiveArch: %{zig_arches}` causes build failure in Fedora koji. This happens because koji srpm buildroot is populated with packages from @srpm-build group only (and that does not include zig-rpm-macros). In absense of the macros.zig, rpm will fail to resolve the `%zig_arches` macro and include it in the ExclusiveArch tag literally instead. On the next step, koji would attempt to extract the list of architectures from the srpm and fail to do find any supported. Example failed task: https://koji.fedoraproject.org/koji/taskinfo?taskID=92342564, which I worked around by inlining the %zig_arches definition in my spec file. --- The common solution is to split out a macro file with a single definition (`%zig_arches ...`) into a separate `zig-srpm-macros` package and add it to the list of dependencies for redhat-rpm-config: https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/rawhide/f/redhat-rpm-config.spec#_109 You may notice that some of the *-srpm-macros are split from the language source packages (https://src.fedoraproject.org/rpms/{rust,fpc,nim}-srpm-macros are good examples). The reason is simple: any problem with a direct dependency of redhat-rpm-macros or an entry in @srpm-build will break the srpm buildroot. Separate source package ensures that a potential issue with the language package, including retirement or disappearance from the build tag, does not break everything. tl;dr: we need a new source package `zig-srpm-macros` with a single file `/usr/lib/rpm/macros.d/macros.zig-srpm` containing a single line `%zig_arches ...`, which then should be added to redhat-rpm-config dependencies.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
I can see `zig-srpm-macros` being pulled into the buildroot for recent rebuildSRPM tasks, so it should be fixed on rawhide. Jan, are you planning to add the macros for stable releases?
I thought about it, but I think its best to get 0.11 into Rawhide first. I'm open to add it to Fedora 39 later.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.