Call to gpgme_check_version is required when using gpgme >= 1.2.0

Bug #452194 reported by Miguel Di Ciurcio Filho on 2009-10-15
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
PyGPGME
High
Jelmer Vernooij

Bug Description

When using gpgme >= 1.2.0 the function gpgme_check_version() must be called before
gpgme_new() [1]. Not calling it causes a GPG_ERR_NOT_OPERATIONAL error.

The file src/pygpgme-context.c needs to be updated.

[1] http://www.gnupg.org/documentation/manuals/gpgme/Library-Version-Check.html#Library-Version-Check

Related branches

William Grant (wgrant) wrote :

This breaks various bits of Launchpad on Lucid.

Jelmer Vernooij (jelmer) on 2010-03-18
Changed in pygpgme:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Jelmer Vernooij (jelmer)
James Henstridge (jamesh) wrote :

Fix merged as r69.

Changed in pygpgme:
milestone: none → 0.2
status: In Progress → Fix Committed
Jelmer Vernooij (jelmer) on 2011-01-28
tags: added: verified
Jelmer Vernooij (jelmer) on 2011-02-10
tags: removed: verified
Robert Collins (lifeless) wrote :

We could do with a release and an SRU to lucid.

Changed in pygpgme:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers