Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests failure due to GPGME behavior change on gpgme_op_verify #471

Open
manphiz opened this issue Dec 6, 2024 · 0 comments
Open

Tests failure due to GPGME behavior change on gpgme_op_verify #471

manphiz opened this issue Dec 6, 2024 · 0 comments

Comments

@manphiz
Copy link

manphiz commented Dec 6, 2024

GPGME has now added "--verify" when invoking "gpg" which changed the behavior on gpgme_op_verify that results in gpg.Context.verify returning empty strings. See the Debian bug[1] for more details of the failure, and GPGME upstream bug[2] and commit[3] for more details of the GPGME change. This was done for GPGME 1.24.0 and backported to 1.23.2.

PGPy should update its tests to adapt to this new behavior.

[1] https://bugs.debian.org/1086378
[2] https://dev.gnupg.org/T6907
[3] https://dev.gnupg.org/rM1dc44b7c5b9253206af527721212d1f55532a7ee

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant