Bug 2097101
| Summary: | python-nipy fails to build with the latest setuptools version | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Charalampos Stratakis <cstratak> |
| Component: | python-nipy | Assignee: | Igor Raits <igor.raits> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | igor.raits, lbalhar, neuro-sig |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-nipy-0.5.0-5.fc37 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-06-27 17:21:37 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: | 2064842 | ||
|
Description
Charalampos Stratakis
2022-06-14 21:51:34 UTC
Also, the package currently fails to build from source because it seems to be incompatible with Python 3.11, see the failure in Koschei: https://koschei.fedoraproject.org/package/python-nipy - it fails in %build so it's not possible to reproduce the problem with setuptools which is in %check on this line: https://src.fedoraproject.org/rpms/python-nipy/blob/rawhide/f/python-nipy.spec#_119 IIUC the core of the problem is that the sources generated by Cython upstream are not regenerated during the RPM build so they are outdated from Python 3.11 perspective even when Cython is able to generate code compatible with Python 3.11. FEDORA-2022-7a2bc77d5e has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7a2bc77d5e FEDORA-2022-7a2bc77d5e has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |