frr fails to build with Python 3.8.0b3. checking for x86_64-redhat-linux-gnu-python3-config... no checking for x86_64-redhat-linux-gnu-python-config... no checking for x86_64-redhat-linux-gnu-python2-config... no checking for x86_64-redhat-linux-gnu-python3.6-config... no checking for x86_64-redhat-linux-gnu-python3.5-config... no checking for x86_64-redhat-linux-gnu-python3.4-config... no checking for x86_64-redhat-linux-gnu-python3.3-config... no checking for x86_64-redhat-linux-gnu-python3.2-config... no checking for x86_64-redhat-linux-gnu-python2.7-config... no checking for python3-config... python3-config checking whether we found a working Python version... no no checking for PYTHON (python-3.6)... no checking for PYTHON (python-3.5)... no checking for PYTHON (python-3.4)... no checking for PYTHON (python-3.3)... no checking for PYTHON (python-3.2)... no checking for PYTHON (python-2.7)... no For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.8/fedora-rawhide-x86_64/00994419-frr/ For all our attempts to build frr with Python 3.8, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.8/package/frr/ 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.8: https://copr.fedorainfracloud.org/coprs/g/python/python3.8/ Let us know here if you have any questions.
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.
I created a PR in upstream github: https://github.com/FRRouting/frr/pull/4836 Is there a timeline for python releases somewhere?
> Is there a timeline for python releases somewhere? Each has its own timeline. For 3.8 it is here: https://www.python.org/dev/peps/pep-0569/#release-schedule They're listed at: https://devguide.python.org/#status-of-python-branches
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
I am postponing this since like you stated in comment #5, some dependencies are not there yet. Namely other python3 packages like python3-pytest and python3-sphinx still require python-3.7. I will try this again in a couple of days.
The f32-python side tag has been merged. In order to rebuild the package, do it in regular rawhide, but please wait until python3-3.8 is tagged: $ koji wait-repo f32-build --build python3-3.8.0~b3-3.fc32 If your built already started in f32-python, after it is finished, please tag it to rawhide with: $ koji tag-build f32-pending <nvr> For example: $ koji tag-build f32-pending libreoffice-6.3.0.4-3.fc32 Thanks! (This comment is mass posted to all bugzillas blocking the PYTHON38 tracking bug.)
(Python 3.8 has landed in the rawhide buildroot.)
This was rebuild with Python 3.8 and I'm closing it in bulk. In case you wanted to keep this bugzilla open because the fix is not ideal, please reopen. Thanks.