Summary: | emerging anything does not work at all anymore! | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Stefan Behte (RETIRED) <craig> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED INVALID | ||
Severity: | blocker | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stefan Behte (RETIRED)
2005-07-19 08:15:58 UTC
This is not something that we can really account for. It seems like somehow the python installation is broken. To fix it, the easiest way is probably to untar a stage3 somewhere else, emerge --buildpkg python and then unpack the resulting package found in /usr/portage/packages/All into the root of your broken system. While from a idealistic standpoint all stuff that fails should be in a try-catch block someplace, I can't imagine adding the thousands of blocks needed in stable. Portage will not function without a complete python installation. I would follow Jasons advice above, or grab a binary package from one of the developers who maintain rescue packages, avenj for example. http://dev.gentoo.org/~avenj/bins/ |