After I do emerge --sync. Portage says me an new version of portage available. So I do emerge -av portage and server say to me: #emerge -av portage These are the packages that would be merged, in order: Calculating dependencies \ !!! All ebuilds that could satisfy ">=dev-lang/python-2.5" have been masked. !!! One of the following masked packages is required to complete your request: - dev-lang/python-2.5.4-r2 (masked by: required EAPI 1, supported EAPI 0) - dev-lang/python-2.5.2-r7 (masked by: required EAPI 1, supported EAPI 0) - dev-lang/python-2.5.2-r8 (masked by: required EAPI 1, supported EAPI 0) - dev-lang/python-2.6-r5 (masked by: required EAPI 2, supported EAPI 0) # Ali Polatel <hawking@gentoo.org> (05 Oct 2008) # Masked until packages that don't work with it are fixed. # see bug #230205 for more info - dev-lang/python-2.6.1 (masked by: required EAPI 2, supported EAPI 0) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (dependency required by "dev-python/pycrypto-2.0.1-r8" [ebuild]) # emerge -s portage * sys-apps/portage Latest version available: 2.1.6.7 Latest version installed: 2.1.2.2 Size of files: 608 kB Homepage: http://www.gentoo.org/proj/en/portage/index.xml Description: Portage is the package management and distribution system for Gentoo License: GPL-2 Reproducible: Always
Do you have "dev-lang/python" in your /etc/portage/package.unmask file?
That's what you get if you fail to update for so long. First try 'emerge -1 --nodeps portage', if that works, "problem" should be gone.
(In reply to comment #1) > Do you have "dev-lang/python" in your /etc/portage/package.unmask file? Forget that, it's completely unrelated. You have to update portage in steps... Try this: emerge -av =portage-2.1.4* and if that works, proceed with emerge -av portage (In reply to comment #2) > That's what you get if you fail to update for so long. > > First try 'emerge -1 --nodeps portage', if that works, > "problem" should be gone. That won't work as his installed portage-version is not EAPI-1 aware.
Thanks it seems that problem has gone. with emerge -1 --nodeps portage when I've tried emerge -av =portage-2.1.4* I've the same problem. Thanks to all
Actually, that worked only because all portage ebuilds still seem to be EAPI="0".