Bug 1900660

Summary: libnuml fails to build with Python 3.10: cmake wrongly detects Python 3.1 instead of Python 3.10
Product: [Fedora] Fedora Reporter: Tomáš Hrnčiar <thrnciar>
Component: libnumlAssignee: Antonio T. sagitter <trpost>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mhroncok, thrnciar
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: 2020-11-25 10:08:41 UTC 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: 1890881    

Description Tomáš Hrnčiar 2020-11-23 13:47:09 UTC
libnuml fails to build with Python 3.10.0a2.

-- Installing: /builddir/build/BUILDROOT/libnuml-1.1.1-23.20190327gite61f6d5.fc34.x86_64/usr/lib64/python3.1/site-packages/libnuml/_libnuml.so

cmake wrongly detects Python 3.1 instead of Python 3.10.

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.10/fedora-rawhide-x86_64/01772947-libnuml/

For all our attempts to build libnuml with Python 3.10, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.10/package/libnuml/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.10:
https://copr.fedorainfracloud.org/coprs/g/python/python3.10/

Let us know here if you have any questions.

Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Antonio T. sagitter 2020-11-25 10:08:41 UTC
Fixed with build release libnuml-1.1.1-24.20190327gite61f6d5