Created attachment 955810 [details] Fix Tests fail due incorrect search location. On AArch64 and s390x, ld*.so is in /lib, not in /lib64 (it's link to /lib64, but...), this results in incorrect search location(/lib). And on AArch64 ld*.so is searched in /lib64 as ordinary lib.so, but should be searched in /lib. I have prepared patch fixing both issues(1st lddtree.py (follow links), 2nd lddtree.sh(if ld*.so, don't follow links, search /lib(64) accordingly instead )). I have tested it on all fedora archs. Successful scratch builds: http://koji.fedoraproject.org/koji/taskinfo?taskID=8055988 http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=2173523 http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=2774962 http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1602908 I have been unsure how/where to contact upstream, feel free to relay the patch to them.
Thanks for the patch, I'll forward it upstream when time permits. In the meantime, an updated build is on its way.
pax-utils-0.9.2-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/pax-utils-0.9.2-1.fc21
Package pax-utils-0.9.2-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pax-utils-0.9.2-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-16159/pax-utils-0.9.2-1.fc21 then log in and leave karma (feedback).
pax-utils-0.9.2-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
i've fixed lddtree.py in a different way: http://git.overlays.gentoo.org/gitweb/?p=proj/pax-utils.git;a=commitdiff;h=8115dc905a772153a1cebaf06ca4f0ba2e257caa i didn't update lddtree.sh though ... - the proposed change simply looks wrong (you can't hardcode any path) - lddtree.sh doesn't have the safe readlink helper that operates on a root - the script already runs `strings` to extract the compiled-in paths - it seems to do the right thing already this is all in pax-utils-1.0.2 now btw: feel free to cc me on future pax-utils reports