diff options
author | Thomas Jost <schnouki@schnouki.net> | 2012-01-20 10:39:24 +0100 |
---|---|---|
committer | David Bremner <bremner@debian.org> | 2012-01-21 08:52:34 -0400 |
commit | 00b5623d1a21d886b564d031e30749e5d02e4ae6 (patch) | |
tree | 68e97bcdc3bb57fb450f1dae112a629f821f88ca /test | |
parent | d3aa6848da4519f6229426b1d0432afacf748f8b (diff) |
Add compatibility with gmime 2.6
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:"8762i8hrb9.fsf@bookbinder.fernseed.info".
This was tested against both gmime 2.6.4 and 2.4.31. With gmime 2.4.31, the
crypto tests all work fine (as expected). With gmime 2.6.4, one crypto test is
currently broken (signature verification with signer key unavailable), most
likely because of a bug in gmime which will hopefully be fixed in a future
version.
Diffstat (limited to 'test')
-rwxr-xr-x | test/crypto | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/test/crypto b/test/crypto index 0af4aa8a..446a58b7 100755 --- a/test/crypto +++ b/test/crypto @@ -104,6 +104,8 @@ test_expect_equal \ "$expected" test_begin_subtest "signature verification with signer key unavailable" +# this is broken with current versions of gmime-2.6 +(ldd $(which notmuch) | grep -Fq gmime-2.6) && test_subtest_known_broken # move the gnupghome temporarily out of the way mv "${GNUPGHOME}"{,.bak} output=$(notmuch show --format=json --verify subject:"test signed message 001" \ |