Bug 2209821

Summary:	automake: Fix python version check for 3.11+
Product:	Red Hat Enterprise Linux 8	Reporter:	Ben Woodard <woodard>
Component:	automake	Assignee:	Frédéric Bérat <fberat>
Status:	VERIFIED ---	QA Contact:	Lenka Špačková <lkuprova>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.8	CC:	codonell, databases-maint, fjanus, fweimer, hhorak, mcermak, praiskup, sipoyare
Target Milestone:	rc	Keywords:	Bugfix, Patch, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	automake-1.16.1-8.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ben Woodard 2023-05-24 22:46:22 UTC

Description of problem:
When python 3.11 is available the version string comes back as 3.1

checking for gawk... gawk
...
checking for system type (linux-gnu)... Linux
checking for python3... python3
checking for python version... 3.1

it kind of looks like you need to add a couple more entries to _AM_PYTHON_INTERPRETER_LIST in /usr/share/aclocal-1.16/python.m4

AC_DEFUN([AM_PATH_PYTHON],
 [
  dnl Find a Python interpreter.  Python versions prior to 2.0 are not
  dnl supported. (2.0 was released on October 16, 2000).
  m4_define_default([_AM_PYTHON_INTERPRETER_LIST],
[python python2 python3 dnl
 python3.9 python3.8 python3.7 python3.6 python3.5 python3.4 python3.3 dnl
 python3.2 python3.1 python3.0 dnl
 python2.7 python2.6 python2.5 python2.4 python2.3 python2.2 python2.1 dnl
 python2.0])

3.10 and 3.11 are lazily matched to 3.1

Version-Release number of selected component (if applicable):
 automake-1.16.1-7.el8.noarch

How reproducible:
always.

Actual results:
3.1

Expected results:
3.11

Additional info:

Comment 1 Ben Woodard 2023-05-24 22:50:02 UTC

This also seems to affect Fedora38 which defaults to python 3.11 and so it probably needs to fan out to other distro versions and be fixed upstream.

Comment 2 Ben Woodard 2023-05-25 16:10:02 UTC

apparently this was fixed in 1.16.3 can we get at least that version in the distros?
https://lists.gnu.org/archive/html/info-gnu/2020-11/msg00005.html