Summary: | sys-apps/portage-2.1.3.19: emerge crashes immediately regardless of parameters | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Lenno Nagel <lenno> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | critical | CC: | denrdc |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lenno Nagel
2007-12-21 20:10:55 UTC
If you have issues w/ >=portage-2.1.3.19 then reopen this bug; we won't fix non-existant versions. Yes, I do have issues with >=sys-apps/portage-2.1.3.19 -- that is what the bug is about. It seems that you have a stale portage module in PYTHONPATH. When portage-2.1.2 is installed, it updates PYTHONPATH in /etc/env.d, but you won't get the updated value in your shell until you source /etc/profile. To identify the stale portage module, do this: ls -d /usr/lib*/portage On a normal system, you should only get one result for that. It's a good idea to remove the stale one that is triggering your problem. The one that you want to keep should be in new PYTHONPATH that's listed inside /etc/env.d/05portage.envd. Sometimes people who have this problem also have incorrect /lib* amd/or /usr/lib* symlinks. The correct layout for an amd64 profile is /lib -> lib64 and /usr/lib -> lib64. This won't be an issue once everyone has >=portage-2.1.2 (in the 2007.1 stages) so I guess we can neglect it. *** Bug 206910 has been marked as a duplicate of this bug. *** |