This bug is a tracker for all GnuPG2 migration issues. Previously we had BOTH GnuPG 1.4 and GnuPG 1.9 installed on systems, and in future there will be only GnuPG 2.0. See 159623 (seahorse) for an example of the changes that MIGHT be neccisary. Seahorse hardcoded checks for 1.2 and 1.4, and thus failed on GnuPG 2.0. There was a check in the configure script, as well as inside the seahorse-agent code. There are no other changes that are required, as the 1.* interface is preserved in 2.0.
app-crypt/gnupg-2.0.1-r2 breaks smartcard support. google doesn't provide any useful info. ssb> 1024R/7F4A1F96 created: 2006-06-23 expires: never card-no: 0001 00000799 Command> scdaemon[16350]: updating status of slot 0 to 0x0007 scdaemon[16350]: client pid is 16349, sending signal 12 scdaemon[16350.0] DBG: <- [EOF] scdaemon[16350]: handler for fd -1 terminated scdaemon[16350]: scdaemon (GnuPG) 2.0.1 stopped gpg: OpenPGP card not available: IPC write error Command>
Mike: Can you please open a new bug for this issue? And try to add verbose to ~/.gnupg/gpg-agent.conf
GnuPG-2.0 badly works with net-im/psi-0.10.2. The problem is that when psi wants to ask the passphrase, it (psi) shows the dialog box with entry for the passphrase. But gnupg shows its own dialog box at the same time (I suppose, the reason is that the command line option for reading passphrase from file descriptor has changed in gnupg-2.0). The passphrase entered in Psi's dialog box is ignored by GnuPG. One can enter the passphrase into the GnuPG's dialog box, but it is not saved, so GnuPG will ask for it again and again.
I think we can close this now... :) Seems alright.
