Summary: | portage 2.0.50-r11 emerge no longer works | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Richard Freeman <rich0> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Richard Freeman
2004-10-21 04:32:48 UTC
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. |