There seem to be more portage errors in the last weeks ... I got a new one:

Code:

FOGELNEST root # emerge -pu world

These are the packages that I would merge, in order.

Calculating world dependencies /Traceback (most recent call last):
File "/usr/bin/emerge", line 1224, in ?
if not mydepgraph.syscreate(getworldlist()):
File "/usr/bin/emerge", line 510, in syscreate
if not self.create(self.match(myline,mykey="update (likely old /var/db/pkg entry)")):
File "/usr/bin/emerge", line 463, in create
if not self.create(mynew,mybigkey):
File "/usr/bin/emerge", line 463, in create
if not self.create(mynew,mybigkey):
File "/usr/bin/emerge", line 407, in create
edepend=portage.db[myroot]["porttree"].dbapi.aux_get(mykey,portage.auxdbkeys)
File "/usr/lib/python2.2/site-packages/portage.py", line 2563, in aux_get
self.auxcache[mycpv][auxdbkeys[x]]=mylines[x][:-1]
IndexError: list index out of range

I wanted to upgrade to gnome2, upgraded portage from 2.0.5 first, then I got stuck at the above error. I do not get this error when emerge -pu gnome-core or any other package, but it also breaks the same way when trying emerge -pu system. (emerge rsync is up2date)

.. Any help welcome!

* ElCondor pasa *_________________Here I am the victim of my own choices and I'm just starting!

You will have to emerge unmerge portage 2.0.7. It seems that emerge does not "clean" up or remove a package when it installs a new package. Some one could correct me if I am wrong, but it would be nice if emerge would remove all the packages that we just updated.

the last installed portage seems to be protected by default, so this works. with 2.0.5 ORBit didn't compile, now I hope that portaging around is done for the moment. (Currently emerge -bu world is doing fine at the 12th package)

* ElCondor pasa *_________________Here I am the victim of my own choices and I'm just starting!