Stuck maxima builds on aarch64

[Jerry James]

I fixed the mass rebuild FTBFS errors for clisp and ecl yesterday, and
started a build of maxima due to changes in both clisp and ecl.
Something is afoot.

There are two previous builds for maxima that both claim to be in the
building state, but were started quite a long time ago:

19 Dec 2016: https://koji.fedoraproject.org/koji/buildinfo?buildID=826479
12 Jan 2017: https://koji.fedoraproject.org/koji/buildinfo?buildID=833415

Then there is my attempt from yesterday:

https://koji.fedoraproject.org/koji/buildinfo?buildID=861874

In all 3 cases, the build finished successfully on all architectures
except aarch64.  But I'm puzzled as to what is going on with my latest
build attempt.  The build log for aarch64 says, in its entirety:

Mock Version: 1.3.3
Mock Version: 1.3.3
ENTER ['do'](['bash', '--login', '-c',
'/usr/bin/rpmbuild -bs --target
aarch64 --nodeps /builddir/build/SPECS/maxima.spec'],
logger=<mockbuild.trace_decorator.getLog object at
0xffff7e8c3390>user='mockbuild'printOutput=Falseshell=Falseuid=1000env={'HOME':
'/builddir', 'PROMPT_COMMAND': 'printf
"\\033]0;<mock-chroot>\\007"',
'SHELL': '/bin/bash', 'PS1': '<mock-chroot> \\s-\\v\\$
', 'TERM':
'vt100', 'LANG': 'en_US.UTF-8', 'PATH':
'/usr/bin:/bin:/usr/sbin:/sbin', 'HOSTNAME':
'mock'}gid=425chrootPath='/var/lib/mock/f26-build-7778919-700214/root'timeout=172800)
Executing command: ['bash', '--login', '-c',
'/usr/bin/rpmbuild -bs
--target aarch64 --nodeps /builddir/build/SPECS/maxima.spec'] with env
{'HOME': '/builddir', 'PROMPT_COMMAND': 'printf
"\\033]0;<mock-chroot>\\007"', 'SHELL': '/bin/bash',
'PS1':
'<mock-chroot> \\s-\\v\\$ ', 'TERM': 'vt100',
'LANG': 'en_US.UTF-8',
'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'HOSTNAME':
'mock'} and shell
False
sh: ecl: command not found
Building target platforms: aarch64
Building for target aarch64
Wrote: /builddir/build/SRPMS/maxima-5.39.0-4.fc26.src.rpm
Child return code was: 0

So ... the source RPM was built successfully, even though ecl was not
found.  Then why wasn't the build launched?  Looking at root.log, it
looks like a dnf transaction has stalled.  The last lines are:

DEBUG util.py:435:  Total
7.7 MB/s |  32 MB     00:04
DEBUG util.py:435:  Running transaction check
DEBUG util.py:435:  Transaction check succeeded.
DEBUG util.py:435:  Running transaction test
DEBUG util.py:435:  Transaction test succeeded.
DEBUG util.py:435:  Running transaction

Except the transaction is not running.  I guess that "sh:ecl: command
not found" is due to this line in the spec file:

%global ecllib %(ecl -eval "(princ (SI:GET-LIBRARY-PATHNAME))" -eval
"(quit)")

but that doesn't seem to have been fatal for the SRPM building step,
and should evaluate just fine during the actual build.  So what's
going on?
-- 
Jerry James
http://www.jamezone.org/