checking for python3.5... /usr/bin/python3.6 checking whether /usr/bin/python3.6 version is >= 3.5... no configure: error: Python interpreter is too old !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-libs/volume_key-0.3.11/work/volume_key-0.3.11/config.log ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib_libressl_20180714-115334 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python3.7 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) [2] ruby25 (with Rubygems) * emerge -qpv dev-libs/volume_key [ebuild N ] dev-libs/volume_key-0.3.11 USE="{-test}" PYTHON_SINGLE_TARGET="python3_6 -python3_5 -python3_7" PYTHON_TARGETS="python3_6 -python3_5 -python3_7"
Created attachment 540804 [details] emerge-info.txt
Created attachment 540806 [details] dev-libs:volume_key-0.3.11:20180724-100935.log
Created attachment 540808 [details] emerge-history.txt
Created attachment 540810 [details] environment
Created attachment 540812 [details] etc.portage.tbz2
Created attachment 540814 [details] logs.tbz2
Created attachment 540816 [details] temp.tbz2
On my dev machine: checking for python3.5... /usr/bin/python3.6 checking whether /usr/bin/python3.6 version is >= 3.5... yes checking for /usr/bin/python3.6 version... 3.6 How did you manage to get a different result here?
yesterday all tinderox images got problems with python deps - I throw away most of them. I'm pretty sure that either the tree was inconsistent or some other sort of oddity happened yesterday.
