[Bug 1089497] New: libzypp tests failure with GNuPG 2.2.6
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497 Bug ID: 1089497 Summary: libzypp tests failure with GNuPG 2.2.6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers@forge.provo.novell.com Reporter: astieger@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- libzypp build fails to build with GnuPG 2.2.6. (or the other way around, 2.2.6 breaks libzypp): [ 491s] The following tests FAILED: [ 491s] 16 - Fetcher_test (Failed) [ 491s] 17 - FileChecker_test (Failed) [ 491s] 20 - KeyRing_test (Failed) [ 491s] 65 - RepoSigcheck_test (Failed) [ 491s] 67 - YUMDownloader_test (Failed) [ 491s] 68 - Downloader_test (Failed) [ 491s] Errors while running CTest As seen in: https://build.opensuse.org/request/show/595102 https://build.opensuse.org/project/monitor/home:AndreasStieger:f I'll debug a bit but maybe you have better visibility. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c1
--- Comment #1 from Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c2
--- Comment #2 from Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c3
Andreas Stieger
gpg: Emit FAILURE stati now in almost all cases. [...] This makes it easier to detect errors by tools which have no way to get the exit code (e.g. due to double forking).
GnuPG-bug-id: 3872 [https://dev.gnupg.org/T3872]
Reverting this commit from GnuPG 2.2.6 allows the libzypp tests to pass. So either it is a problem in GnuPG, or libzypp calls (via gpgme) GnuPG in a way that causes the newly introduced failure states to trigger. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c4
Benjamin Zeller
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c5
--- Comment #5 from Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c8
--- Comment #8 from Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c9
--- Comment #9 from Benjamin Zeller
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c10
--- Comment #10 from Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c11
--- Comment #11 from Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c12
Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497
http://bugzilla.opensuse.org/show_bug.cgi?id=1089497#c13
Andreas Stieger
The fix is in GnuPG.
gpgme, of course. https://build.opensuse.org/request/show/597073 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com