FS#66572 - [gpgme] t-json test fails

Attached to Project: Arch Linux
Opened by Andreas Baumann (andreas_baumann) - Thursday, 07 May 2020, 06:17 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 30 March 2022, 11:01 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

FAIL: t-json

Additional info:
* package version(s): 1.13.1-4 and

Steps to reproduce:
asp export core/gpgme (or asp export gpgme)
cd gpgme
staging-x86_64-build
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 30 March 2022, 11:01 GMT
Reason for closing:  Works for me
Additional comments about closing:  fixed
Comment by Christian Hesse (eworm) - Thursday, 07 May 2020, 12:26 GMT
Builds fine with gnupg-2.2.19, but fails with gnupg-2.2.20...
Comment by Christian Hesse (eworm) - Friday, 08 May 2020, 11:37 GMT
Reported upstream:
https://lists.gnupg.org/pipermail/gnupg-devel/2020-May/034599.html
Comment by Allan McRae (Allan) - Saturday, 23 May 2020, 02:54 GMT
Had a quick look at this - appears to be an issue with output changes and not necessarily a bug in gpg or gpgme.
Comment by loqs (loqs) - Sunday, 27 September 2020, 14:52 GMT
I re-enabled the test and could not produce the issue.
I reverted 5c0d1c7f76c95bad8bce4ad3bafd121ec5101d3c still passed, reverting cff600f1f65a2164ab25ff2b039cba008776ce62 and the test fails with the same message.
cff600f1f65a2164ab25ff2b039cba008776ce62 was committed in January 2020 which would have been in the git master eworm tested so perhaps something else changed.

Loading...