Thomas Jost(schnouki@schnouki.net)@170112-00:56: > 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 > fails (signature verification with signer key unavailable) but this will be hard > to fix since the new API does not report the reason why a signature verification > fails (other than the human-readable error message). +1 from me. I literally just coded up a similar patch, and the first email I see with the newly compiled notmuch is this one. I've now tried Thomas's (better) patch with gmime-2.6.4 and notmuch 7ddd849015759a329bf8fef8c8b5a93359408962, and can confirm it works fine for me. This build breakage is otherwise quite painful. Thanks Thomas. Tim -- Tim Stoakes