Bug 1889732

This is a problem in automake. The documentation says: 

PYTHON_VERSION
The Python version number, in the form major.minor (e.g., ‘2.5’). This is currently the value of ‘sys.version[:3]’.

https://www.gnu.org/software/automake/manual/html_node/Python.html



The code seem to actually use this naïve construct:

[automake (master)]$ rg -F 'sys.version'
m4/python.m4
94:    [am_cv_python_version=`$PYTHON -c "import sys; sys.stdout.write(sys.version[[:3]])"`])
127:    if python_implementation() == 'CPython' and sys.version[[:3]] == '2.7':
230:# word of sys.version), in order to cope with versions such as 2.2c1.

doc/automake.texi
7861:@samp{sys.version[:3]}.

t/python-virtualenv.sh
46:py_version=$(python -c 'import sys; print("%u.%u" % tuple(sys.version_info[:2]))')

t/python-vars.sh
31:PYTHON_VERSION=$($PYTHON -c 'import sys; print(sys.version[:3])') || exit 1




Patrik, could you please report this to upstream? I am not subscribed to their mailing lists.

Here's my attempted fix: https://src.fedoraproject.org/rpms/automake/pull-request/3

It moves the build of the rpm package further, but there are some new failures (most likely unrelated):

https://copr.fedorainfracloud.org/coprs/g/python/python3.10/build/1717510/

The rpm failures are mostly:

error: /build/RPMS/noarch/....rpm: open failed: No such file or directory
error: cannot open ... index using sqlite - Operation not permitted (1)
error: cannot open Packages database in /var/lib/rpm
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file or directory)
error: failed to stat /data/SPECS/....spec: No such file or directory
error: open of /build/RPMS/noarch/....rpm failed: No such file or directory
error: package ... is not installed
error: Unable to open sqlite database /var/lib/rpm/rpmdb.sqlite: unable to open database file

I get the same failures when I try to build rpm in a clean copr (first build with defaults, second with mock bootstrap):

https://copr.fedorainfracloud.org/coprs/churchyard/rpm-experiment/builds/

Same results with local mock build.

The test failures are not automake nor Python 3.10 related at all.

My proposed automake fix should be enough to fix the build failure.

Ough, something broke fakechroot big time. I remember seeing something about recent glibc changes breaking this and that, and whenever something changes, fakechroot is one of the first things to blow up...

Upstream bug report:

https://lists.gnu.org/archive/html/bug-automake/2020-10/msg00022.html

FEDORA-2020-5bc8c37539 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

This needs to be backported, because developers will use automake on stable Fedoras to generate tarballs to be used in rawhide packages.

FEDORA-2020-6e4db46b53 has been pushed to the Fedora ELN stable repository.
If problem still persists, please make note of it in this bug report.

This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

The Fedora 33 and 32 build were garbage collected. Could this please be backported to Fedora 33?

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

FEDORA-2021-d5291e5172 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d5291e5172

Patch was already backported to f33. Made a rebuild and submitted to Bodhi.

FEDORA-2021-d5291e5172 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d5291e5172`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d5291e5172

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2021-d5291e5172 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Interesting, I see it still happening with newer automake:

ykaul@ykaul glusterfs]$ rpm -q automake
automake-1.16.2-5.fc35.noarch

[ykaul@ykaul glusterfs]$ grep am_cv_python_version configure
if ${am_cv_python_version+:} false; then :
  am_cv_python_version=`$PYTHON -c "import sys; sys.stdout.write(sys.version[:3])"`
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_python_version" >&5
$as_echo "$am_cv_python_version" >&6; }
  PYTHON_VERSION=$am_cv_python_version

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days