The pygpgme unit tests don't complete, instead bringing up the gtk pinentry dialog.
Up to now, my digging points to gpg2 simply not allowing passphrases through a file descriptor and only through a gpg-agent. However, I'm not convinced because the app, 'sigul', part of the Fedora buildsys software, was working a couple of months ago on Fedora 17 (that's a difference I'll explore today).
I'd appreciate pointers for where to look next. I'm happy to help debug, not afraid of the source, and it appears I have a live manifestation of the above bug, but I'm unfamiliar with gnupg.
Hi, I'm having the same problem. Fedora 16, pygpgme 0.3, gpgme 1.3.0, gnupg 2.0.18.
I posted to the gnupg-users list while debugging over a couple of days. See the latest message here:
http:// lists.gnupg. org/pipermail/ gnupg-users/ 2012-September/ 045417. html
The pygpgme unit tests don't complete, instead bringing up the gtk pinentry dialog.
Up to now, my digging points to gpg2 simply not allowing passphrases through a file descriptor and only through a gpg-agent. However, I'm not convinced because the app, 'sigul', part of the Fedora buildsys software, was working a couple of months ago on Fedora 17 (that's a difference I'll explore today).
I'd appreciate pointers for where to look next. I'm happy to help debug, not afraid of the source, and it appears I have a live manifestation of the above bug, but I'm unfamiliar with gnupg.