You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By using ExcludeArch on an arch by arch basis, it enables the majority of packages to have the chance to build on new alternative architectures, rather than being immediately ignored by a blanket ExclusiveArch. There is a process running that will notify architecture maintainers of all changes in Exclude and Exclusive Arch headers along with daily summaries of all packages with architecture specific handling
We are routinely building our packages (and testing them) on architectures upstream maintainers have no access to (e.g., s390x, ppc64le, or from smaller ones riscv64, and loongarch64) and we can help upstream to at least test them if they do not whitelist.
The text was updated successfully, but these errors were encountered:
https://github.com/CodSpeedHQ/pytest-codspeed/blob/003c3b4660ce34754990f14b9f949ad0d6a1c46d/setup.py#L23C1-L26C2
I couldn’t explain it better than my colleagues from Fedora:
We are routinely building our packages (and testing them) on architectures upstream maintainers have no access to (e.g.,
s390x
,ppc64le
, or from smaller onesriscv64
, andloongarch64
) and we can help upstream to at least test them if they do not whitelist.The text was updated successfully, but these errors were encountered: