I get a traceback during updating portage cache at the end of sync: >>> Updating Portage cache... \Traceback (most recent call last): File "/usr/bin/emerge", line 2070, in ? mymatches=portage.portdb.xmatch("match-all",x) File "/usr/lib/portage/pym/portage.py", line 4592, in xmatch myval=match_from_list(mydep,self.cp_list(mykey)) File "/usr/lib/portage/pym/portage.py", line 3258, in match_from_list raise KeyError, "Specific key requires an operator (%s)" % (mydep) KeyError: 'Specific key requires an operator (packages/powerpc-unknown-linux-gnu-3.2)' All my systems have PKGDIR="${PORTDIR_OVERLAY}/packages/${CHOST}-3.2", and the overlay is shared over NFS. When I comment out the OVERLAY and PKGDIR settings, I don't hit the error. (commenting out the PKGDIR isn't enough)
I assume it's caused because "packages" is a valid category in $PORTDIR/profiles/categories so portage "thinks" your $PORTDIR_OVERLAY/packages/${CHOST}-3.2 is a package (as in ebuild) directory. Options are: - we remove "packages" from the categories file (does anyone know why it's in there ?) - you move your packages dir out of your PORTDIR_OVERLAY - you rename it so it doesn't have the same name as a category - we try to hack around it
well I've had this setup for a long time, it just broke like this in 50_pre*
Yes, 2.0.50 doesn't like cat/pkg-version entries anymore (except for injecting).
I got the same error after emerging portage-2.0.50.ebuild (stable build?) today. All portage commands threw this error and I had to use the portage-rescue package to fix. Here's an example. I ran etc-update after emerging 2.0.50. # etc-update Traceback (most recent call last): File "/usr/lib/portage/bin/portageq", line 9, in ? import portage,types,string File "/usr/lib/portage/pym/portage.py", line 6377, in ? for y in db["/"]["porttree"].dbapi.xmatch("match-all", x): File "/usr/lib/portage/pym/portage.py", line 4688, in xmatch myval=match_from_list(mydep,self.cp_list(mykey)) File "/usr/lib/portage/pym/portage.py", line 3531, in match_from_list raise KeyError, "Specific key requires an operator (%s) (try adding an '=')" % (mydep) KeyError: "Specific key requires an operator (dev-perl/mod_perl-1.99.10) (try adding an '=')" Traceback (most recent call last): File "/usr/lib/portage/bin/portageq", line 9, in ? import portage,types,string File "/usr/lib/portage/pym/portage.py", line 6377, in ? for y in db["/"]["porttree"].dbapi.xmatch("match-all", x): File "/usr/lib/portage/pym/portage.py", line 4688, in xmatch myval=match_from_list(mydep,self.cp_list(mykey)) File "/usr/lib/portage/pym/portage.py", line 3531, in match_from_list raise KeyError, "Specific key requires an operator (%s) (try adding an '=')" % (mydep) KeyError: "Specific key requires an operator (dev-perl/mod_perl-1.99.10) (try adding an '=')" Scanning Configuration files... Exiting: Nothing left to do; exiting. :)
Chris, guessing this is no longer an issue?
Closing... shouldn't be possible now, further, hasn't reared it's head.