Bug 1899132
Summary: | python-caja fails to build with Python 3.10: configure truncates 3.10 to 3.1 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomáš Hrnčiar <thrnciar> |
Component: | python-caja | Assignee: | Wolfgang Ulbrich <fedora> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | fedora, mhroncok, patrick, 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-19 10:20:06 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-18 15:23:57 UTC
This is an automake problem that has been fixed upstream end of last october. Release 1.24.0 has been prepared with an automake older than this date and has latched the bugous macro into aclocal.m4. @Wolfgang: There is two ways to fix it: 1) Issue a new upstream release prepared with a very recent automake, then package it. You have to do it. 2) Have a "BR: autoconf" and an "autoreconf -fi" at end of %prep section. I can do it (https://koji.fedoraproject.org/koji/taskinfo?taskID=55817651). You decide... please tell. Option (2) is my recommendation. That way you always use the latest fixes when the Fedora package is built, instead of having to do (1) any tome something is wrong with the pre-generated configure. It is also consistent with the suggested idea of rebuilding everything in Fedora instead of shipping pre-generated files in SRPM: https://docs.fedoraproject.org/en-US/packaging-guidelines/what-can-be-packaged/#_pregenerated_code > That way you always use the latest fixes when the Fedora package is built...
On the other way, autogen/buildconf process is done when generating an upstream release from SCM and systematically redoing it for an upatched release is not very elegant !
Patrick, you can run `NOCONFIGURE=1 ./autogen.sh` after `%autosetup` because MATE ships `autogen.sh` in all tarballs. Btw, mate-common pulls in `autoconf` as runtime require. https://src.fedoraproject.org/rpms/mate-common/blob/master/f/mate-common.spec#_12 As Mate upstream folk i prefer to re-run autogen to fix the issue. We include `autogen` ecactly for this case to avoid preparing a new tarball for a leightweight problem probably caused by a thirdparty. This should do it: https://koji.fedoraproject.org/koji/taskinfo?taskID=55864617 Builds successfully in mock with python 3.10. Thanks for the hints. Thanks. |