| Summary: | Portage is crashing whenever using -upD | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Stephen <siti_veni> |
| Component: | Unclassified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Had this problem a few hours ago too. Re-synced a minute ago, and emerge world -Dup wanted to downgrade portage (before it broke). Re-emerged portage, the problem disappeared, and a new minor one appeared. Some perl modules were blocking the due perl upgrade, and were themselves due for an upgrade. I just unmerged the blocking modules and let portage get on with the world update. No problems here with portage-2.0.48-r7. What version do you have? |
Portage crashes when doing anything simlair to this: emerge -upD world emerge -upD portage etc. Reproducible: Always Steps to Reproduce: 1.emerge -upD world 2. 3. Actual Results: traceback (always the same): emerge -upD mozilla These are the packages that I would merge, in order: Calculating dependencies ...done! Traceback (most recent call last): File "/usr/bin/emerge", line 1978, in ? mydepgraph.display(mydepgraph.altlist()) File "/usr/bin/emerge", line 943, in display if ("fetch" in string.split(portage.portdb.aux_get(x[2],["RESTRICT"])[0])): File "/usr/lib/python2.2/site-packages/portage.py", line 3423, in aux_get myebuild,in_overlay=self.findname2(mycpv) File "/usr/lib/python2.2/site-packages/portage.py", line 3392, in findname2 for myloc in suffix_array(self.overlays, "/"+mysplit[0]+"/"+psplit[0]+"/"+mysplit[1]+".ebuild"): TypeError: unsubscriptable object Expected Results: worked