6307 – portage 2.0.27 crashes on emerge -u world with PORTDIR_OVERLAY

Bug 6307 - portage 2.0.27 crashes on emerge -u world with PORTDIR_OVERLAY

Summary: portage 2.0.27 crashes on emerge -u world with PORTDIR_OVERLAY

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-08-10 18:29 UTC by Jacob Perkins
Modified:	2011-10-30 22:21 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jacob Perkins 2002-08-10 18:29:52 UTC

I can emerge packages fine with PORTDIR_OVERLAY, but when I do 'emerge -u world
-p' I get:
Calculating world dependencies \Traceback (most recent call last):
  File "/usr/bin/emerge", line 1315, in ?
    if not mydepgraph.xcreate(myaction):
  File "/usr/bin/emerge", line 749, in xcreate
    myeb=portage.portdb.xmatch("bestmatch-visible",mydep)
  File "/usr/lib/python2.2/site-packages/portage.py", line 2955, in xmatch
    myval=best(self.xmatch("match-visible",None,mydep,mykey))
  File "/usr/lib/python2.2/site-packages/portage.py", line 2966, in xmatch
    myval=self.match2(mydep,mykey,self.xmatch("list-visible",None,mydep,mykey))
  File "/usr/lib/python2.2/site-packages/portage.py", line 2952, in xmatch
    myval=self.gvisible(self.visible(self.cp_list(mykey)))
  File "/usr/lib/python2.2/site-packages/portage.py", line 3030, in gvisible
    myaux=db["/"]["porttree"].dbapi.aux_get(mycpv, ["KEYWORDS"])
  File "/usr/lib/python2.2/site-packages/portage.py", line 2844, in aux_get
    self.auxcache[mycpv][auxdbkeys[x]]=mylines[x][:-1]
IndexError: list index out of range

If I comment out PORTDIR_OVERLAY, then everything works fine.
If it matters, gcc3.1.1

Comment 1 Maurizio Disimino 2002-08-26 08:24:56 UTC

same problem with portage .28 ?

Comment 2 Jacob Perkins 2002-08-26 10:34:29 UTC

line numbers have changed, but yes, still have problem

Comment 3 Daniel Robbins (RETIRED) gentoo-dev

2002-09-03 16:35:42 UTC

Portage 2.0.34 should give you a sane error message; closing this bug.

Comment 4 Jacob Perkins 2002-09-03 17:16:21 UTC

actually 2.0.34 gives no error, everythings fine