[PATCH] build: Require gmime >= 2.6.7

2012-03-13 Thread David Bremner
On Sun, 11 Mar 2012 22:29:46 -0300, David Bremner wrote: > From: Thomas Jost > > gmime-2.6 had a bug [1] which made it impossible to tell why a signature > verification failed when the signer key was unavailable (empty "sigstatus" > field > in the JSON output). Since 00b5623d the corresponding

Re: [PATCH] build: Require gmime >= 2.6.7

2012-03-13 Thread David Bremner
On Sun, 11 Mar 2012 22:29:46 -0300, David Bremner wrote: > From: Thomas Jost > > gmime-2.6 had a bug [1] which made it impossible to tell why a signature > verification failed when the signer key was unavailable (empty "sigstatus" > field > in the JSON output). Since 00b5623d the corresponding

[PATCH] build: Require gmime >= 2.6.7

2012-03-13 Thread Tomi Ollila
On Sun, 11 Mar 2012 22:29:46 -0300, David Bremner wrote: > From: Thomas Jost > > gmime-2.6 had a bug [1] which made it impossible to tell why a signature > verification failed when the signer key was unavailable (empty "sigstatus" > field > in the JSON output). Since 00b5623d the corresponding

Re: [PATCH] build: Require gmime >= 2.6.7

2012-03-13 Thread Tomi Ollila
On Sun, 11 Mar 2012 22:29:46 -0300, David Bremner wrote: > From: Thomas Jost > > gmime-2.6 had a bug [1] which made it impossible to tell why a signature > verification failed when the signer key was unavailable (empty "sigstatus" > field > in the JSON output). Since 00b5623d the corresponding

[PATCH] build: Require gmime >= 2.6.7

2012-03-11 Thread David Bremner
From: Thomas Jost gmime-2.6 had a bug [1] which made it impossible to tell why a signature verification failed when the signer key was unavailable (empty "sigstatus" field in the JSON output). Since 00b5623d the corresponding test is marked as broken when using gmime-2.6 (2.4 is fine). This bug

[PATCH] build: Require gmime >= 2.6.7

2012-03-11 Thread David Bremner
From: Thomas Jost gmime-2.6 had a bug [1] which made it impossible to tell why a signature verification failed when the signer key was unavailable (empty "sigstatus" field in the JSON output). Since 00b5623d the corresponding test is marked as broken when using gmime-2.6 (2.4 is fine). This bug