Command ['/usr/bin/asciidoc', '--version'] returned 127 * ERROR: net-misc/ntpsec-1.1.2::gentoo failed (configure phase): * configure failed * * Call stack: * ebuild.sh, line 124: Called src_configure ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_20180916-215051 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) [2] ruby25 (with Rubygems) * emerge -qpv net-misc/ntpsec [ebuild N ] net-misc/ntpsec-1.1.2 USE="seccomp -debug -doc -early -gdb -heat -libressl -nist -ntpviz -rclock_arbiter -rclock_generic -rclock_gpsd -rclock_hpgps -rclock_jjy -rclock_local -rclock_modem -rclock_neoclock -rclock_nmea -rclock_oncore -rclock_pps -rclock_shm -rclock_spectracom -rclock_trimble -rclock_truetime -rclock_zyfer -samba -smear -tests" PYTHON_TARGETS="python2_7 python3_6 -python3_4 -python3_5"
Created attachment 547188 [details] emerge-info.txt
Created attachment 547190 [details] emerge-history.txt
Created attachment 547192 [details] environment
Created attachment 547194 [details] etc.portage.tbz2
Created attachment 547196 [details] logs.tbz2
Created attachment 547198 [details] net-misc:ntpsec-1.1.2:20180918-115416.log
Created attachment 547200 [details] temp.tbz2
the contents of /var/tmp/portage/net-misc/ntpsec-1.1.2/work/ntpsec-1.1.2-python3_6/build/config.log might leave a clue as to why asciidoc decided to fail in such an atypical fashion.
(In reply to James Browning from comment #8) see attached logs.tbz2
I suspect (after most of a month being useless) that this is the result of a misconfiguration possibly in eselect python. the not root cause is a python wrapper shell script that prints out an error message and dies w/ exit code 127.
No longer in the tree
