| Summary: | emerge pukes up strange error codes when using -f flag | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Andy <noisefactor> |
| Component: | Core | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2.0 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Known issue. Fixed in the 2.0.48 series. |
I got the following error after having emerged the openoffice-bin-1.1_beta.ebuild. [That fails on setup because some files are missing (icons), so I tried to fetch the source distribution to find the missing files.] Then the following happened, which I don't think is good: emerge --fetchonly openoffice Calculating dependencies ...done! Traceback (most recent call last): File "/usr/bin/emerge", line 1862, in ? mydepgraph.merge(mydepgraph.altlist()) File "/usr/bin/emerge", line 1098, in merge y=portage.portdb.findname(x[2]) File "/usr/lib/python2.2/site-packages/portage.py", line 3032, in findname return self.root+"/"+mysplit[0]+"/"+psplit[0]+"/"+mysplit[1]+".ebuild" TypeError: unsubscriptable object ----------- I've sync'ed recently.