Summary: | Portage unusable after latest sync (1430 Eastern) - while trying to Perform Global updates (bad variable) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Gary Stein <gstein> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED FIXED | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gary Stein
2003-07-22 11:49:30 UTC
after I was able to fix those line then I could emerge portage-2.0.48-r5 which seems to have these fixes however only diff is: 6c6 < VERSION="2.0.48-r4" --- > VERSION="2.0.48-r5" 3924c3924 < self.remotepkgs = getbinpkgs.dir_get_metadata(settings["PORTAGE_BINHOST"], chunk_size=chunk_size) --- > self.remotepkgs = getbinpkg.dir_get_metadata(settings["PORTAGE_BINHOST"], chunk_size=chunk_size) not sure if the new one (bottom) needs the plural there sorry to bother, you guys fixed too quick, damn you responsive bug fixers.... but since I could not emerge previously because the bug, it might suck for others gary Simplist way is to use a rescue portage. |