Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1943932

Summary: fastavro does not support 32bit architectures
Product: [Fedora] Fedora Reporter: Ankur Sinha (FranciscoD) <sanjay.ankur>
Component: python-fastavroAssignee: Ankur Sinha (FranciscoD) <sanjay.ankur>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: neuro-sig, sanjay.ankur, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 179258, 485251, 1968947    

Description Ankur Sinha (FranciscoD) 2021-03-28 14:19:49 UTC 
Description of problem:
fastavro upstream does not support 32 bit architectures

Version-Release number of selected component (if applicable):
NA

Upstream issue + confirmation: https://github.com/fastavro/fastavro/issues/526
Comment 1 Zbigniew Jędrzejewski-Szmek 2021-06-17 10:48:53 UTC 
This is causing python-dask to ftbfs when it gets scheduled on an arm builder…
Comment 2 Zbigniew Jędrzejewski-Szmek 2021-06-17 11:05:43 UTC 
I think we'd be better off just skipping the tests on 32 bit arches.
When noarch packages build-require an archful package that is only available on some arches,
things become very annoying. Either we have to retry builds until we happen to hit a supported
builder, or make the noarch package archful and propagate the arch exclusions. But this 
propagates through the tree, and is a terrible solution. So actually dumb rebuilding in 
a loop is a better of the two options.