Bug 1897089 - libpst fails to build with Python 3.10: python binary not found
Summary: libpst fails to build with Python 3.10: python binary not found
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: libpst
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Carl Byington
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: PYTHON3.10
TreeView+ depends on / blocked
Reported: 2020-11-12 09:50 UTC by Tomáš Hrnčiar
Modified: 2020-11-12 10:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)

Description Tomáš Hrnčiar 2020-11-12 09:50:52 UTC
libpst fails to build with Python 3.10.0a2.

checking for python build information... 
checking for python3.9... no
checking for python3.8... no
checking for python3.7... no
checking for python3.6... no
checking for python3.5... no
checking for python3.3... no
checking for python3.2... no
checking for python3.1... no
checking for python3.0... no
checking for python2.7... no
checking for python2.6... no
checking for python2.5... no
checking for python2.4... no
checking for python2.3... no
checking for python2.2... no
checking for python2.1... no
checking for python... no
  results of the Python check:
    Binary:      no
    Library:     no
    Include Dir: no
configure: error: python binary not found

Seems like there is missing check for python3.10.

For the build logs, see:

For all our attempts to build libpst with Python 3.10, see:

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.10:

Let us know here if you have any questions.

Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Miro Hrončok 2020-11-12 10:05:16 UTC
The configure script has:

		if test -z "$ac_python_version"; then
			if test -n "$PYTHON_VERSION"; then
				ac_python_version=`$PYTHON -c "import sys; \
					print (sys.version[:3])"`

That's why it doesn't work IMHO:

$ python3.10
>>> import sys
>>> print (sys.version[:3])

Note You need to log in before you can comment on or make changes to this bug.