Summary: | portage 2.0.49-r20 says some ebuilds are invalid, emerge -U world fails | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Benjamin Paul Kay <kc8tbe> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Benjamin Paul Kay
2004-01-01 11:46:56 UTC
that looks like a broken tree As Marius said. Reopen if sync'ing a fresh tree doesn't fix it. Turns out the bug went away by simply rebooting the machine - whether or not this was incidental is uncertain. The reboot was the first reboot since upgrading portage from r19 to r20. I did not the portage rescue program. If a reboot is necessary to sync, fix, or whatever a damaged portage tree, this could be a problem that needs to be addressed in future releases of portage. |