pypy 2.0 is out, but portage fails to build with it as it is specifically checking for pypy1_9. Reproducible: Always Steps to Reproduce: 1. link pypy1_9 to pypy2_0 binary 2. emerge portage with USE="pypy1_9 -python2 -python3" 3. Actual Results: * Messages for package sys-apps/portage-2.2.0_alpha145: * Path to 'python': '/usr/bin/python' * ABI: 'amd64' * DEFAULT_ABI: 'amd64' * EPYTHON: 'pypy-c2.0' * PYTHON_ABI: '2.7-pypy-1.9' * Locally active version of Python: '2.7-pypy-2.0' * ERROR: sys-apps/portage-2.2.0_alpha145 failed (setup phase): * 'python' does not respect EPYTHON variable * * Call stack: * ebuild.sh, line 93: Called pkg_setup * portage-2.2.0_alpha145.ebuild, line 140: Called python_set_active_version '2.7-pypy-1.9' * python.eclass, line 1763: Called _python_final_sanity_checks * python.eclass, line 370: Called die * The specific snippet of code: * die "'python' does not respect EPYTHON variable" * * If you need support, post the output of `emerge --info '=sys-apps/portage-2.2.0_alpha145'`, * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.2.0_alpha145'`. * The complete build log is located at '/mnt/storageData/temp/portage/portage/sys-apps/portage-2.2.0_alpha145/temp/build.log'. * The ebuild environment file is located at '/mnt/storageData/temp/portage/portage/sys-apps/portage-2.2.0_alpha145/temp/die.env'. * Working directory: '/mnt/storageData/temp/portage/portage/sys-apps/portage-2.2.0_alpha145' * S: '/mnt/storageData/temp/portage/portage/sys-apps/portage-2.2.0_alpha145/work/portage-2.2.0_alpha142' Expected Results: Clean install :)
This is fixed in cvs now.
