This is the bug per my email to the crypto herd. gpgme-1* breaks due to passphrase input somewhere. This MUST be fixed before gnupg2 can go stable. # FEATURES=test ebuild gpgme-1.1.4.ebuild test ... (full build process) >>> Test phase [check]: app-crypt/gpgme-1.1.4 Making check in assuan make[1]: Entering directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/assuan' make check-am make[2]: Entering directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/assuan' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/assuan' make[1]: Leaving directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/assuan' Making check in gpgme make[1]: Entering directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/gpgme' make check-am make[2]: Entering directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/gpgme' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/gpgme' make[1]: Leaving directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/gpgme' Making check in tests make[1]: Entering directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/tests' Making check in gpg make[2]: Entering directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/tests/gpg' make check-TESTS make[3]: Entering directory `/dev/shm/portage/app-crypt/gpgme-1.1.4/work/gpgme-1.1.4/tests/gpg' -----BEGIN PGP MESSAGE----- Version: GnuPG v2.0.3 (GNU/Linux) hQEOA2rm1+5GqHH4EAP+L9hlirYH8tJJ09uhr7ONq6IOvxDoe2k6/gGGwQeuxXJb 5VTH5Ljoj3ih8X3L1fJ//OvSxz3DFjm9QEmAL0ZFwMxMDhQPt8NeDREcIlPPuIWT mtg0EjHJ7sxrPs83wSl4gapkRcT2s4IqfIGVnzax4W+4TrUluNgQhaTkf+x4CkMD /jQCSkl6PnC5+DjXxqBO0ENT9180ELbKGlIoRUvFMrx6z+WsXS7/pfM4ijlCikBF fCtbZQVKIJiHqtMH9ItCvXWSW4v0ZsDba4rP4j98bN7g0VonD0p58Qjq3o4dR4zJ 0BsADd3lUCQ7ctsB3xQsByYfrffudziInLfHxlEJOhT6hQEOA1OB6k7im6N/EAP/ Zd2qGJiTcUjKPrCFB/MNsEdtU1X+Q74iqHnuhWWTra114pNWHQvm9dUXoC1oxVYJ 9wuL0cdJQ8hKTINAkZqGqHVa0wsBMXmLbkW/Rwvd71CmZOXVDJxwUFfBAge9jOeC r5F9WmvauFUm26zz8nAceV+QIbMaUcoCksPEeVVMEhQD/3w2/ARFBi42TXHaMeAC ez6DXIl+1bKYPFiMNY6qvs7TGSFgJBCuBeC8423cyd15tR8TUuIrttnMZufgDo5p gjcAuT/TYY7zhxesasXY9SJGhKVNpvq1Eat2lM8u6tLehyeT74BoStgv3bkN3QSS Xz7ELGwe0UxQzJ638t4FJP7J0kcBonawMa2xRuIIbBM8ALM89mV/sBDleb617l43 IptkupnRqyBSHpcPuAibYcUU15Gppw4KMebZt69YTiwR4GShHK15BqKvgg== =umwu -----END PGP MESSAGE----- PASS: t-encrypt (hangs here, sometimes pinentry comes up). Interrupted. make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs.... make[3]: *** wait: No child processes. Stop. make[2]: *** [check-am] Error 2 make[1]: *** [check-recursive] Interrupt make: *** [check-recursive] Interrupt
alonbl, please work on this bug, high priority. Potential plans of action (pick one or more) - Trace it to a specific gnupg build where this error was introduction. - Debug inside gpgme calls.
alonbl, please keep the gpgme stuff on this bug. alonbl wrote this in an email to me: >> With only gnupg2 installed, do this: >> FEATURES=test ebuild gpgme-1.1.4.ebuild test > > Please don't run interactive tests under sandbox. > I compiled gpgme and run make check and all tests passed. > I even disable the built-in agent disabling and use one daemon and > password caching is working. Ok, it DOES still happen even outside of the sandbox. Here is the complete test output: http://dev.gentoo.org/~robbat2/gnupg_gpgme_passphrase_problems_20070314.typescript I just hit Enter whenever pinentry came up to ask for input. Basically I do: ebuild gnupg-2.0.3.ebuild compile cd /location/to/$S make check (this one passes fine) ebuild gpgme-1.1.4.ebuild compile cd /location/to/$S make check (pinentry comes up several times)
(In reply to comment #2) > I just hit Enter whenever pinentry came up to ask for input. You need to specify "abc" whenever pinentry come up. And then it will work.
robbat2: Please reopen if you still have an issue with this.
