Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 55F5E431FAF for ; Fri, 20 Jan 2012 14:45:44 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cZtWS1tg5LEm for ; Fri, 20 Jan 2012 14:45:43 -0800 (PST) Received: from guru.guru-group.fi (guru-group.fi [87.108.86.66]) by olra.theworths.org (Postfix) with ESMTP id 9DA76431FAE for ; Fri, 20 Jan 2012 14:45:43 -0800 (PST) Received: by guru.guru-group.fi (Postfix, from userid 501) id 3C30868055; Sat, 21 Jan 2012 00:45:47 +0200 (EET) From: Tomi Ollila To: Thomas Jost , notmuch@notmuchmail.org Subject: Re: [PATCH v4 2/3] Add compatibility with gmime 2.6 In-Reply-To: <1327052365-20012-2-git-send-email-schnouki@schnouki.net> References: <87fwfaemuc.fsf@thor.loria.fr> <1327052365-20012-1-git-send-email-schnouki@schnouki.net> <1327052365-20012-2-git-send-email-schnouki@schnouki.net> User-Agent: Notmuch/0.11+71~gefa5d6c (http://notmuchmail.org) Emacs/23.3.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 22:45:44 -0000 On Fri, 20 Jan 2012 10:39:24 +0100, Thomas Jost wrote: > 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. > --- +1 Tomi