| Summary: | sys-apps/portage-2.1.6.7 All ebuilds that could satisfy ">=dev-lang/python-2.5" have been masked. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Daniel Simao <daniel.simao> |
| Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Daniel Simao
2009-03-07 18:51:10 UTC
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". |