Bug 1829770

Summary: gpgme: FTBFS in rawhide
Product: [Fedora] Fedora Reporter: Marcel Plch <mplch>
Component: gpgmeAssignee: Igor Raits <igor.raits>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: igor.raits, mhroncok, python-maint, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gpgme-1.13.1-7.fc33 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-30 13:12:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1785415, 1803234    

Description Marcel Plch 2020-04-30 10:05:58 UTC 
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.
Comment 1 Igor Raits 2020-04-30 10:08:52 UTC 
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.
Comment 2 Igor Raits 2020-04-30 10:10:32 UTC 
Just curious, can you test it with patch from https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commit;h=b97434fbf087f3176daf39699ff579d38d265317?
Comment 3 Marcel Plch 2020-04-30 10:33:39 UTC 
Same result.
Comment 4 Tomas Mraz 2020-04-30 13:12:48 UTC 
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.
Comment 5 Igor Raits 2020-04-30 13:24:25 UTC 
(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.