Call to gpgme_check_version is required when using gpgme >= 1.2.0
Bug #452194 reported by
Miguel Di Ciurcio Filho
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PyGPGME |
Fix Released
|
High
|
Jelmer Vernooij |
Bug Description
When using gpgme >= 1.2.0 the function gpgme_check_
gpgme_new() [1]. Not calling it causes a GPG_ERR_
The file src/pygpgme-
[1] http://
Related branches
lp://qastaging/~jelmer/pygpgme/bug452194
- Michael Hudson-Doyle (community): Approve
- James Henstridge: Pending requested
-
Diff: 1868 lines (+544/-303)24 files modifiedMakefile (+1/-1)
gpgme/__init__.py (+1/-1)
gpgme/tests/test_context.py (+20/-0)
gpgme/tests/test_delete.py (+0/-1)
gpgme/tests/test_editkey.py (+5/-2)
gpgme/tests/test_encrypt_decrypt.py (+38/-16)
gpgme/tests/test_export.py (+7/-4)
gpgme/tests/test_genkey.py (+7/-4)
gpgme/tests/test_import.py (+8/-5)
gpgme/tests/test_passphrase.py (+8/-5)
gpgme/tests/test_progress.py (+6/-3)
gpgme/tests/test_sign_verify.py (+27/-24)
setup.py (+12/-8)
src/gpgme.c (+40/-6)
src/pycompat.h (+49/-0)
src/pygpgme-context.c (+148/-118)
src/pygpgme-data.c (+17/-9)
src/pygpgme-error.c (+48/-20)
src/pygpgme-genkey.c (+6/-6)
src/pygpgme-import.c (+26/-20)
src/pygpgme-key.c (+36/-22)
src/pygpgme-keyiter.c (+1/-2)
src/pygpgme-signature.c (+31/-26)
src/pygpgme.h (+2/-0)
- James Henstridge: Approve
-
Diff: 26 lines (+10/-0)1 file modifiedsrc/gpgme.c (+10/-0)
Changed in pygpgme: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Jelmer Vernooij (jelmer) |
tags: | added: verified |
tags: | removed: verified |
Changed in pygpgme: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This breaks various bits of Launchpad on Lucid.