Summary: | sys-apps/portage-2.1_pre5-r2 fails on emerge --metadata/--sync, UnboundLocalError: local variable 'myf' referenced before assignment | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Thomas Cort (RETIRED) <tcort> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | alpha, tcort |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | Alpha | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Thomas Cort (RETIRED)
2006-03-02 16:27:53 UTC
I upgraded to sys-apps/portage-2.1_pre5-r2 and encountered the same problem. Before this problem occured, there was a power outage and the machine went down without a proper shutdown. After booting and fsck'ing, everything appeared to be fine. However, just now the file system journal aborted and automatically remounted the partition as read-only. After several reboots and full fscks, the journal keeps randomly aborting. I'm going to close this bug as INVALID because it may be due to the screwed up file system. I'll do a fresh install, and if the portage error comes up again, then I'll reopen the bug. |