See https://copr.fedorainfracloud.org/coprs/g/python/python3.8/package/telepathy-gabble/ for actual logs. This report is automated and not very verbose, but feel free to ping me for help.
I cannot really parse the problem, but this is suspicious (xrange is Python 2 code): Configure summary: Compiler Flags.......: -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection + make -j2 Traceback (most recent call last): File "../tools/xincludator.py", line 36, in <module> xincludate(dom, argv[0]) File "../tools/xincludator.py", line 14, in xincludate for i in xrange(dom.documentElement.attributes.length): NameError: name 'xrange' is not defined make[2]: *** [Makefile:612: _gen/all.xml] Error 1 make[1]: *** [Makefile:376: all-recursive] Error 1 make: *** [Makefile:306: all] Error 2 Could you please have a look at the problem?
Could you please respond.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
The coordinated rebuild of Python 3.8 has started in the `f32-python` side tag. If you figure out how to rebuild this package, please don't rebuild it in regular rawhide, but use the side tag instead: on branch master: $ fedpkg build --target=f32-python To wait for a build to show up in the side tag, do: $ koji wait-repo f32-python --build=<nvr> Where <nvr> is name-version-release of the source package, e.g. python-foo-1.1-2.fc32. An updated mock config is posted at: http://copr.fedorainfracloud.org/coprs/g/python/python3.8/ Note that it will take a while before the essential packages are rebuilt, so don't expect all your dependencies to be available right away. Thanks. Let us know if you need up to date info, or if you have any questions. PS this message is mass posted to all the bugs that block the PYTHON38 bug. If this is also a Fedora 31 FTBFS bug and you manage to fix it, you can do a f31 build as usual: on branch f31: $ fedpkg build
*** This bug has been marked as a duplicate of bug 1736897 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days