>> "If your currently installed version of python reported by python -V >> is less than 2.6 then you must choose a version of portage that is >> compatible with it. If you have at least python 2.6 then use >> portage-2.1.10.41.tar.bz2. If you have python 2.4 or 2.5 then use >> portage-2.1.6.tar.bz2." >> >> I get: >> >> # python -V >> Python 2.5.2 >> >> and I'm already on portage-2.1.6.13 which is non-functional since it >> doesn't have high enough EAPI support for current ebuilds. >> >> I think I'm stuck between a python and portage upgrade. I can't >> update python with my current portage and I can't update portage with >> my current python. > > The blockages you posted relate to Python 2.7 and the latest portage. > What happens if you install python:2.6, either through portage or a > tarball. > > Try emerge -1a python:2.6
I get: # emerge -1a python:2.6 [snip] [ebuild NS ] dev-lang/python-2.6.7-r2 [2.5.2-r7] USE="gdbm ncurses readline ssl threads (wide-unicode) xml -berkdb -build -doc -examples -ipv6 -sqlite -tk -wininst" [blocks B ] >=dev-lang/python-2.6.6:2.6 (">=dev-lang/python-2.6.6:2.6" is blocking sys-apps/portage-2.1.6.13) [blocks B ] <sys-apps/portage-2.1.9 ("<sys-apps/portage-2.1.9" is blocking dev-lang/python-2.6.7-r2) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. ('ebuild', '/', 'dev-lang/python-2.6.7-r2', 'merge') pulled in by python:2.6 - Grant