I just upgraded python to 2.3.4, and portage to 2.0.50-r11, due to both being marked stable. emerge no longer works - at all... root # emerge -pu world Traceback (most recent call last): File "/usr/bin/emerge", line 10, in ? import portage File "/usr/lib/portage/pym/portage.py", line 6878, in ? portdb=portdbapi(settings["PORTDIR"]) File "/usr/lib/portage/pym/portage.py", line 4900, in __init__ self.manifestVerifier = portage_gpg.FileChecker(self.mysettings["PORTAGE_GPG_DIR"], "gentoo.gpg", requireSignedRing=True, minimumTrust=self.manifestVerifyLevel) File "/usr/lib/portage/pym/portage_gpg.py", line 46, in __init__ raise portage_exception.DirectoryNotFound, "keydir: %s" % keydir portage_exception.DirectoryNotFound: 'keydir: ' Hopefully this is fairly easy to correct manually, as I am unable to emermge anything at the moment... Reproducible: Always Steps to Reproduce: 1. 2. 3. emerge info Traceback (most recent call last): File "/usr/bin/emerge", line 10, in ? import portage File "/usr/lib/portage/pym/portage.py", line 6878, in ? portdb=portdbapi(settings["PORTDIR"]) File "/usr/lib/portage/pym/portage.py", line 4900, in __init__ self.manifestVerifier = portage_gpg.FileChecker(self.mysettings["PORTAGE_GPG_DIR"], "gentoo.gpg", requireSignedRing=True, minimumTrust=self.manifestVerifyLevel) File "/usr/lib/portage/pym/portage_gpg.py", line 46, in __init__ raise portage_exception.DirectoryNotFound, "keydir: %s" % keydir portage_exception.DirectoryNotFound: 'keydir: '
You've got PORTAGE_GPG_DIR in make.conf? Seems like that it the reason for the traceback.
You are using 2.0.51 and you have gpg enabled in FEATURES.
Actually, I'm using 2.0.50-r11. I did notice the bugs for 2.0.51 and gpg. If this is in fact a dupe I'll see what resolutions they suggest (it sounds like removing gpg from the features list would be one - although it would probably be better to move in the direction of standardizing gpg support than crippling it).
Who is 'they'? By Crippling you mean "making it actually work"?
They = the 2.0.51 portage gpg bug already filed. As far as making it work goes - after reading that bug I'm starting to get a better feeling for what is going on here. It sounds like gpg support was added as a stub, and never really worked. In the upgrade they started adding some functionality, but it now requires some configuration (putting a keyring in a specific place) - otherwise portage breaks. This is still a bug - it should at least spit out a meaningful error message. However, I agree that the protage team seems to be moving in the right direction. In any case, I filed the bug since I didn't see any obvious ones already. I think you can probably safely mark this as a dupe of 68371.
*** This bug has been marked as a duplicate of 68371 ***
