On Thu, Oct 30, 2003 at 12:09:06PM +0100, Michel Wilson wrote: > Hello, > > Since a few days, emerge gives me a weird error when doing an emerge -pu > world. First, it calculates the dependencies, and spits out the packages > it is going to update, just like normally. Then, it comes up with this > cryptic error: > Traceback (most recent call last): > File "/usr/bin/emerge", line 2133, in ? > mydepgraph.display(mydepgraph.altlist()) > File "/usr/bin/emerge", line 1103, in display > elif (not "--emptytree" in myopts) and > portage.db[x[1]]["vartree"].exists_specific_cat(x[2]): > File "/usr/lib/python2.2/site-packages/portage.py", line 3469, in > exists_specific_cat > self.invalidentry(self.root+"var/db/pkg/"+a[0]+"/"+x) > AttributeError: vartree instance has no attribute 'invalidentry' >
I ran into this problem recently when I tried and failed to emerge openoffice. There's a bug report in bugzilla: #31901. There's a comment in the bug report which suggests running /usr/lib/portage/bin/fix-db.py to fix the problem. This didn't fix the problem in my case, but it did reveal a couple of leftovers from the openoffice merge. Something like: /var/db/pkg/app-office/.../-MERGING-openoffice-1.1.0 /var/db/pkg/app-office/.../-MERGING-openoffice-1.1.0.portage_lockfile I deleted them and the problem went away. - PK > Very informative. > > When updating some packages, it complains about > >>> Auto-cleaning packages ... > !!! Invalid db entry: /var/db/pkg/*sys-fs/devfsd > So I suspect something is wrong with that entry. I re-emerged devfsd > already, but that didn't help. Also, an emerge sync didn't make the > problem go away. > What is wrong here, and where should I look to fix it? > > Regards, > > Michel. > > -- > [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
