Bug#689147: unblock: gajim/0.15.1-1
On 12/12/2012 03:41 PM, intrigeri wrote:
Hi,
Yann Leboulanger wrote (12 Dec 2012 11:50:25 GMT) :
Ok then we wait for an answer from secure-testing-team?
I think so.
I don't think I need to do somthing, do I?
I think you don't, now that I added them to the loop myself.
Which means we can now get back to why this update of an embedded
library should be unblocked. Why is this update needed? Is the version
embedded in testing / in unstable (based on) the same as the one
packaged in python-gnupg?
this version of Gajim doesn't only fix this embedded library
But the version embedded fixes some unhandeled errors, as I told you in
the previous mail. Full diff against python-gnupg-0.3.0 attached
--
Yann
--- /usr/share/pyshared/gnupg.py 2012-10-23 01:42:18.000000000 +0200
+++ gnupg.py 2012-12-02 19:43:09.000000000 +0100
@@ -64,7 +64,7 @@
except NameError:
_py3k = True
-logger = logging.getLogger(__name__)
+logger = logging.getLogger('gajim.c.gnupg')
if not logger.handlers:
logger.addHandler(NullHandler())
@@ -435,6 +435,7 @@
self.gpg = gpg
self.type = None
self.fingerprint = None
+ self.status = ''
def __nonzero__(self):
return self.fingerprint is not None
@@ -448,6 +449,8 @@
if key in ("USERID_HINT", "NEED_PASSPHRASE", "BAD_PASSPHRASE",
"GOOD_PASSPHRASE", "BEGIN_SIGNING", "CARDCTRL"):
pass
+ elif key in ("KEYEXPIRED", "SIGEXPIRED"):
+ self.status = 'key expired'
elif key == "SIG_CREATED":
(self.type,
algo, hashalgo, cls,
Reply to: