Taviso, I think this is yours: gpg-agent requires the presence of pinentry to function properly; since newpg and gnupg-1.9.10 also both provide gpg-agent, they should block each other. This is masked right now, so it's not a big deal (yet) ;).
actually, it's a runtime dependency, not a build dependency...
Thats true, but you can't run gpgsm (which is part of gnupg-1.9) without pinentry. Perhaps there should be a useflag or somewhat, if you don't want a "real" dependency...
Will this be fixed some day?
Dennis: 1.9.x is not supported, the 1.4.x branch is being maintained by another crypto developer and I maintain the 1.2.x branch, however there is now a new gpg-agent package for those who require it...if this is the only reason you are using the 1.9.x branch, i _highly_ reccomend dropping back to a supported branch and using the gpg-agent package instead..although it doesnt look like it depends on pinentry either, is that an issue? if so, let me know and I'll get it sorted out.
*** Bug 76015 has been marked as a duplicate of this bug. ***
resolved -> WONTFIX.
