Description of problem: Upstream test suite is failing upon build. Version-Release number of selected component (if applicable): 1.13.1-6 How reproducible: Always Steps to Reproduce: $ fedpkg clone gpgme $ cd gpgme $ fedpkg mockbuild Actual results: FAIL: t-json stopping gpg-agent PASS: final.test ======================================= 1 of 3 tests failed Please report to https://bugs.gnupg.org ======================================= make[4]: Leaving directory '/builddir/build/BUILD/gpgme-1.13.1/tests/json' make[4]: *** [Makefile:609: check-TESTS] Error 1 make[3]: Leaving directory '/builddir/build/BUILD/gpgme-1.13.1/tests/json' make[3]: *** [Makefile:732: check-am] Error 2 make[2]: Leaving directory '/builddir/build/BUILD/gpgme-1.13.1/tests/json' make[2]: *** [Makefile:734: check] Error 2 make[1]: Leaving directory '/builddir/build/BUILD/gpgme-1.13.1/tests' make[1]: *** [Makefile:720: check-recursive] Error 1 make: *** [Makefile:534: check-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.378h5u (%check) Expected results: Test suite should pass.
I think this is due to update of gnupg2 from 2.2.19-1.fc32 to 2.2.20-1.fc33. I'll try to check as soon as I can.
Just curious, can you test it with patch from https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commit;h=b97434fbf087f3176daf39699ff579d38d265317?
Same result.
The regression is happening already with gnupg-2.2.19. I've fixed it in Rawhide - the patch is from https://dev.gnupg.org/T4820 However the patch is not yet fully upstream. As I have builds of gnupg-2.2.20 for all active Fedora releases, it would be a good idea to create gpgme updates for them with the patch (just merging the master should be OK IMHO). But I am leaving that up to the gpgme maintainers decision.
(In reply to Tomas Mraz from comment #4) > The regression is happening already with gnupg-2.2.19. > > I've fixed it in Rawhide - the patch is from > https://dev.gnupg.org/T4820 > > However the patch is not yet fully upstream. > > As I have builds of gnupg-2.2.20 for all active Fedora releases, it would be > a good idea to create gpgme updates for them with the patch (just merging > the master should be OK IMHO). But I am leaving that up to the gpgme > maintainers decision. If you can handle this, would appreciate this much.