Summary: | emerge rsync results in KeyError | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Kaleb Pederson <kaleb.pederson> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED CANTFIX | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kaleb Pederson
2004-03-25 12:20:39 UTC
This one is similar to 41400 BTW, but given the age of that bug, I don't think it has been taken care of. Please run `grep -r app-doc/ebook-gtk-2.0 /var/cache/edb /etc/portage /usr/local/portage` root@kinux kibab # grep -r app-doc/ebook-gtk-2.0 /var/cache/edb /etc/portage /usr/local/portage /var/cache/edb/eclass.pickle:aS'app-doc/ebook-gtk-2.0-r1' grep: /etc/portage: No such file or directory grep: /usr/local/portage: No such file or directory Hello Kaleb, The problem happens yet? If so, can try this command? # PORTDIR_OVERLAY="" emerge sync The problem disappeared after I did my next rsync. The sync itself was working it was the computations after the sync that caused it to die. I verified that I had nothing in PORTDIR_OVERLAY related to that ebuild, as I guessed that was the intent of the command the previous poster listed (even though he didn't grab my PORTDIR_OVERLAY from the emerge info). These were what I had (and still have) in PORTDIR_OVERLAY ./net-www/tomcat/tomcat-4.1.29.ebuild (and supporting files) ./net-fs/samba/samba-3.0.1.ebuild (and supporting files) ./dev-python/yappy/yappy-1.2.1.ebuild (and supporting files) None of the above reference any gnome particulars. I generally don't need to do many custom ebuilds, so my ebuilds shouldn't have been related to the problem. I haven't changed them since before the sync that caused the problem, nor have I changed them since... That's an extremely weird place for that error message and I can only imagine it being caused by something very oddly named in the portage tree... like 'ebook-gtk-2.0-2.0.ebuild' That particular traceback is not recoverable and won't be "fixed". |