1 Return-Path: <BATV+eff4eac810ffdd348d20+2838+infradead.org+hohndel@bombadil.srs.infradead.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id BC9DB431FD0
\r
6 for <notmuch@notmuchmail.org>; Wed, 1 Jun 2011 05:35:42 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=1.676 tagged_above=-999 required=5
\r
12 tests=[RDNS_DYNAMIC=0.363, URI_HEX=1.313] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id QWaIkToa7qYA for <notmuch@notmuchmail.org>;
\r
16 Wed, 1 Jun 2011 05:35:38 -0700 (PDT)
\r
17 Received: from bombadil.infradead.org
\r
18 (173-166-109-252-newengland.hfc.comcastbusiness.net
\r
20 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
21 (No client certificate requested)
\r
22 by olra.theworths.org (Postfix) with ESMTPS id D3137431FB6
\r
23 for <notmuch@notmuchmail.org>; Wed, 1 Jun 2011 05:35:37 -0700 (PDT)
\r
24 Received: from localhost ([127.0.0.1] helo=x201s.gr8dns.org)
\r
25 by bombadil.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux))
\r
26 id 1QRke3-0006nt-03; Wed, 01 Jun 2011 12:35:31 +0000
\r
27 Received: by x201s.gr8dns.org (Postfix, from userid 500)
\r
28 id 46BB07004FA; Wed, 1 Jun 2011 05:35:29 -0700 (PDT)
\r
29 From: Dirk Hohndel <hohndel@infradead.org>
\r
30 To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
\r
31 Subject: Re: compile error of current git on F15
\r
32 In-Reply-To: <4DE51768.3070409@fifthhorseman.net>
\r
33 References: <m3d3j1uz2i.fsf@x201s.gr8dns.org>
\r
34 <8762osjagp.fsf@servo.factory.finestructure.net>
\r
35 <4DE51768.3070409@fifthhorseman.net>
\r
36 User-Agent: Notmuch/0.5-174-g347983b (http://notmuchmail.org) Emacs/23.2.1
\r
37 (x86_64-redhat-linux-gnu)
\r
38 Date: Wed, 01 Jun 2011 05:35:29 -0700
\r
39 Message-ID: <m3ipspbuge.fsf@x201s.gr8dns.org>
\r
41 Content-Type: text/plain; charset=utf-8
\r
42 Content-Transfer-Encoding: quoted-printable
\r
43 X-SRS-Rewrite: SMTP reverse-path rewritten from <hohndel@infradead.org> by
\r
44 bombadil.infradead.org See http://www.infradead.org/rpr.html
\r
45 Cc: notmuch <notmuch@notmuchmail.org>, Jeffrey Stedfast <fejj@novell.com>
\r
46 X-BeenThere: notmuch@notmuchmail.org
\r
47 X-Mailman-Version: 2.1.13
\r
49 List-Id: "Use and development of the notmuch mail system."
\r
50 <notmuch.notmuchmail.org>
\r
51 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
52 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
53 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
54 List-Post: <mailto:notmuch@notmuchmail.org>
\r
55 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
56 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
57 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
58 X-List-Received-Date: Wed, 01 Jun 2011 12:35:42 -0000
\r
60 On Tue, 31 May 2011 12:29:28 -0400, Daniel Kahn Gillmor <dkg@fifthhorseman.=
\r
62 Non-text part: multipart/signed
\r
63 > i'm CC'ing the upstream lead developer of gmime here to see if he has
\r
64 > any thoughts (and can correct any misrepresentations from me) -- Hi Jeffr=
\r
67 > On 05/30/2011 02:43 PM, Jameson Graef Rollins wrote:
\r
68 > > On Sun, 29 May 2011 11:44:05 -0700, Dirk Hohndel <hohndel@infradead.org=
\r
70 > >> CC -O2 notmuch-reply.o
\r
71 > >> notmuch-reply.c: In function =E2=80=98notmuch_reply_command=E2=80=99:
\r
72 > >> notmuch-reply.c:658:3: error: unknown type name =E2=80=98GMimeSession=
\r
74 > >> notmuch-reply.c:659:3: warning: passing argument 1 of =E2=80=98g_mime_=
\r
75 gpg_context_new=E2=80=99 from incompatible pointer type [enabled by default]
\r
76 > >> /usr/include/gmime-2.6/gmime/gmime-gpg-context.h:64:21: note: expected=
\r
77 =E2=80=98GMimePasswordRequestFunc=E2=80=99 but argument is of type =E2=80=
\r
79 > >> make: *** [notmuch-reply.o] Error 1
\r
81 > >> This seems to have been introduced in Jameson's crypto patch series...
\r
83 > >> ./configure shows:
\r
85 > >> Checking for Xapian development files... Yes (1.2.4).
\r
86 > >> Checking for GMime development files... Yes (gmime-2.6).
\r
87 > >> Checking for Glib development files (>=3D 2.14)... Yes.
\r
89 > > Hey, Dirk. Looks like you're using gmime-2.6, which is something I've
\r
90 > > never looked at, and it looks like there are API changes. This of
\r
91 > > course doesn't help you, Dirk, but this probably means we should require
\r
92 > > libgmime-2.4, at least until we can figure out how to support both
\r
93 > > versions, which I'm not sure how to handle.
\r
95 > > Dirk, just out of curiosity, what system are you running that is
\r
96 > > provides gmime 2.6?
\r
98 > F15 probably means Fedora 15.
\r
102 > gmime 2.6 has not been released yet; gmime 2.5 is the development
\r
103 > version (which itself has an unstable API); the project uses the
\r
104 > even=3Dstable/odd=3Dunstable version numbering scheme.
\r
106 > As the dev version, gmime 2.5 identifies itself as 2.6. I'm not sure i
\r
107 > can justify this decision. Jeffrey, can you explain?
\r
109 > If F15 does not have gmime 2.4 available in it, it's possible that it
\r
110 > may not be able to build notmuch :/
\r
112 That's where I am right now. But here's the odd thing: gmime-2.6 support
\r
113 was explicitly added to the configure script last year:
\r
114 http://notmuch.198994.n3.nabble.com/PATCH-configure-Add-support-for-GMime-2=
\r
117 And it's only a recent change to notmuch that broke the build on F15
\r
118 (it's one of the patches for the crypto support).
\r
120 So in my book this is a regression for notmuch!
\r
122 > I don't think that notmuch should attempt to target a library with an
\r
123 > unstable API. But if anyone is interested in preparing for the gmime
\r
124 > 2.6 release (maybe jeffrey can hint at the timeline for us) may want to
\r
125 > prepare changesets that #ifdef the relevant code depending on the API
\r
128 > Once gmime 2.6 is released, we'll need to decide if we want to remain
\r
129 > compatible with the old API as well, or just require gmime 2.6; but i
\r
130 > don't think we need to cross that bridge right now.
\r
132 Given what I wrote above you'll be unsurprised that I don't agree with
\r
133 this interpretation of the situation.
\r
135 This used to work and used to be supported and was broken in a recent
\r