On Mon, 27 Feb 2017 21:02:40 -0700
Jerry James <loganjerry(a)gmail.com> wrote:
On Mon, Feb 27, 2017 at 3:15 PM, Kevin Fenzi <kevin(a)scrye.com>
wrote:
> Hey. I looked at this a few weeks ago... but I don't recall all the
> details so I wanted to look more closely at it again before I
> replied.
>
> However, I have not had time since your orig email on saturday to do
> so.
>
> I'll try and look soon, but I'm afraid you will need some
> patience.
No worries. I didn't realize the git branching was going on when I
sent that. I will be patient. Thanks, Kevin.
Branching hasn't started yet... thats later today. ;)
ok, on to the fun of maxima.
So, on aarch64 (only) it never gets to the point of actually building.
It gets stuck everytime in the dnf call that sets up the root:
├─kojid,24165 /usr/sbin/kojid --fg --force-lock --verbose
│ └─kojid,32174 /usr/sbin/kojid --fg --force-lock --verbose
│ └─mock,32680 -tt /usr/libexec/mock/mock -r koji/f26-build-7778919-700214
--no-clean --target aarch64 ...
│ └─dnf,32726 /usr/bin/dnf builddep --installroot
/var/lib/mock/f26-build-7778919-700214/root//var/lib/moc
in root.log we have a normal looking transaction:
DEBUG util.py:435: Transaction Summary
DEBUG util.py:435:
================================================================================
DEBUG util.py:435: Install 51 Packages
DEBUG util.py:435: Total download size: 32 M
DEBUG util.py:435: Installed size: 132 M
DEBUG util.py:435: Downloading Packages:
DEBUG util.py:435:
--------------------------------------------------------------------------------
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
In the dnf.rpm.log in the chroot we have:
Feb 24 23:54:06 INFO Installed: ecl-16.1.3-1.fc26.aarch64
Feb 24 23:54:06 INFO Installed: desktop-file-utils-0.23-3.fc26.aarch64
Feb 24 23:54:08 INFO Installed: gcl-2.6.12-7.fc26.aarch64
...
Looking at the dnf process fd's:
lrwx------. 1 root root 64 Feb 28 18:39 43 ->
/var/lib/mock/f26-build-7778919-700214/root/var/lib/dnf/history/history-2017-02-24.sqlite-journal
lrwx------. 1 root root 64 Feb 28 18:39 44 ->
/var/lib/mock/f26-build-7778919-700214/root/var/lib/rpm/.rpm.lock
lrwx------. 1 root root 64 Feb 28 18:39 45 ->
/var/lib/mock/f26-build-7778919-700214/root/var/lib/rpm/Supplementname
lrwx------. 1 root root 64 Feb 28 18:39 46 ->
/var/lib/mock/f26-build-7778919-700214/root/var/lib/rpm/Enhancename
lr-x------. 1 root root 64 Feb 28 18:39 47 ->
/var/lib/mock/f26-build-7778919-700214/root/var/cache/yum/build-ef45ecfc50ca7520/packages/time-1.7-52.fc26.aarch64.rpm
lr-x------. 1 root root 64 Feb 28 18:39 48 ->
/var/lib/mock/f26-build-7778919-700214/root/var/cache/yum/build-ef45ecfc50ca7520/packages/time-1.7-52.fc26.aarch64.rpm
So, something about the aarch64 'time' package? Nothing really leaps to
out at a quick glance, and wouldn't other packages hit this? and whats
pulling in the time package anyhow?
I'm not sure where to go from here, but thats the info I have...
Happy to try and gather more.
kevin