gpgme fails to build with Python 3.9.0a2: checking for a Python interpreter with version >= 2.7... none checking for a Python interpreter with version >= 3.4... none checking for a Python interpreter with version >= 3.5... none checking for a Python interpreter with version >= 3.6... none checking for a Python interpreter with version >= 3.7... none checking for a Python interpreter with version >= 3.8... none checking for a Python interpreter with version >= all... none configure: error: *** *** Please install the python development packages. *** Seems like gpgme build system hardcodes a list of Python versions and that list doesn't yet have 3.9. For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01138971-gpgme/ For all our attempts to build gpgme with Python 3.9, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/gpgme/ 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.9: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/ Let us know here if you have any questions. Python 3.9 will be included in Fedora 33, but the initial bootstrapping has already started. A build failure this early in the bootstrap sequence blocks us very much.
This ugly %prep hack gets the job done: +# The configure script does not list Python 3.9 yet +sed -i 's/3.8/%{python3_version}/g' configure It would be nicer to not hardcode the list of Python versions in configure, but ¯\_(ツ)_/¯
Can you please prioritize this?
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
I'm looking into an upstream(able) fix.
Upstream: https://github.com/gpg/gpgme/pull/4 Fedora: https://src.fedoraproject.org/rpms/gpgme/pull-request/6