Your package fails to build with the newest upcoming autoconf-2.71, which is part of a wide Fedora change. Please see the attached copr: https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/. More information about testing your package when building with autoconf available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test
Gentle ping.
I’m not the maintainer. This package routinely pushes the resource limits of the builders: https://bugzilla.redhat.com/show_bug.cgi?id=1771023 https://bugzilla.redhat.com/show_bug.cgi?id=1771024 https://bugzilla.redhat.com/show_bug.cgi?id=1771031 https://bugzilla.redhat.com/show_bug.cgi?id=1771034 I tried a local build with the autoconf-2.71 copr, and the part that regenerates the configure file and runs it completed successfully. (I was not interested in waiting for the whole build to finish.) It looks to me like the COPR build just hits its timeout because this package is so compile-intensive, and there is no autoconf 2.71 bug here after all. See https://download.copr.fedorainfracloud.org/results/odubaj/autoconf-2.70/fedora-rawhide-x86_64/02095867-python-graph-tool/builder-live.log.gz.
If you consider it works properly, you can close this issue. But there is a risk it would not build successfully after merging autoconf-2.71
Thanks for looking into this Ben, Ondrej. At the moment, like Ben, I cannot see anything Autoconf related here in the logs from the most recent build in your COPR: https://download.copr.fedorainfracloud.org/results/odubaj/autoconf-2.70/fedora-rawhide-x86_64/02095867-python-graph-tool/build.log.gz So I'm going to close this, and if it fails again after the merge, we'll have logs from the Fedora builders (that don't time out in 5 hours like COPR) with complete errors.