* Package: net-mail/libpst-0.6.64 * Repository: gentoo * Maintainer: forensics * USE: abi_x86_64 amd64 elibc_glibc kernel_linux python userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox * '/usr/bin/python' is not a valid symlink. * Use `eselect python set ${python_interpreter}` to fix this problem. * ERROR: net-mail/libpst-0.6.64::gentoo failed (setup phase): * '/usr/bin/python' is not a valid symlink * * Call stack: * ebuild.sh, line 133: Called pkg_setup * libpst-0.6.64.ebuild, line 29: Called python_set_active_version '2' * python.eclass, line 1745: Called _python_initial_sanity_checks * python.eclass, line 353: Called die * The specific snippet of code: * die "'${EPREFIX}/usr/bin/python' is not a valid symlink" * * If you need support, post the output of `emerge --info '=net-mail/libpst-0.6.64::gentoo'`, * the complete build log and the output of `emerge -pqv '=net-mail/libpst-0.6.64::gentoo'`. * The complete build log is located at '/var/tmp/portage/net-mail/libpst-0.6.64/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-mail/libpst-0.6.64/temp/die.env'. * Working directory: '/usr/lib64/python3.4/site-packages' * S: '/var/tmp/portage/net-mail/libpst-0.6.64/work/libpst-0.6.64' I guess it has do do with this python test: pkg_setup() { if use python; then python_set_active_version 2 python_pkg_setup fi }
I builds now, I guess the python eclass was updated to handle this case.
