Re: compile error of current git on F15

diff --git a/a6/f746eae51be8efbe0c24bb525ed3492aa73459 b/a6/f746eae51be8efbe0c24bb525ed3492aa73459
new file mode 100644 (file)
index 0000000..50f05f0
--- /dev/null
+++ b/a6/f746eae51be8efbe0c24bb525ed3492aa73459
@@ -0,0 +1,102 @@
+Return-Path: <jrollins@finestructure.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 3DA31431FD0\r
+       for <notmuch@notmuchmail.org>; Wed,  1 Jun 2011 09:55:29 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.29\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id 42orBdv6pbNu for <notmuch@notmuchmail.org>;\r
+       Wed,  1 Jun 2011 09:55:25 -0700 (PDT)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+       [131.215.239.19])\r
+       by olra.theworths.org (Postfix) with ESMTP id 0ECE5431FB6\r
+       for <notmuch@notmuchmail.org>; Wed,  1 Jun 2011 09:55:25 -0700 (PDT)\r
+Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+       by fire-doxen-postvirus (Postfix) with ESMTP id B00C3328095;\r
+       Wed,  1 Jun 2011 09:48:40 -0700 (PDT)\r
+X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
+Received: from servo.finestructure.net (cpe-98-149-172-122.socal.res.rr.com\r
+       [98.149.172.122]) (Authenticated sender: jrollins)\r
+       by fire-doxen-submit (Postfix) with ESMTP id 66A483282C1;\r
+       Wed,  1 Jun 2011 09:48:35 -0700 (PDT)\r
+Received: by servo.finestructure.net (Postfix, from userid 1000)\r
+       id AE9EA7A0; Wed,  1 Jun 2011 09:55:18 -0700 (PDT)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: Dirk Hohndel <hohndel@infradead.org>,\r
+       Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+Subject: Re: compile error of current git on F15\r
+In-Reply-To: <m3ipspbuge.fsf@x201s.gr8dns.org>\r
+References: <m3d3j1uz2i.fsf@x201s.gr8dns.org>\r
+       <8762osjagp.fsf@servo.factory.finestructure.net>\r
+       <4DE51768.3070409@fifthhorseman.net>\r
+       <m3ipspbuge.fsf@x201s.gr8dns.org>\r
+User-Agent: Notmuch/0.6 (http://notmuchmail.org) Emacs/23.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Wed, 01 Jun 2011 09:55:16 -0700\r
+Message-ID: <87oc2hlcej.fsf@servo.factory.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha256; protocol="application/pgp-signature"\r
+Cc: notmuch <notmuch@notmuchmail.org>, Jeffrey Stedfast <fejj@novell.com>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 01 Jun 2011 16:55:29 -0000\r
+\r
+--=-=-=\r
+\r
+On Wed, 01 Jun 2011 05:35:29 -0700, Dirk Hohndel <hohndel@infradead.org> wrote:\r
+> This used to work and used to be supported and was broken in a recent\r
+> notmuch patch.\r
+\r
+Hey, Dirk.  I would actually say that support for gmime 2.6 was merely\r
+coincidental up until now.  For all functionality we had been using, the\r
+API in 2.4 and 2.6 was the same (the patch that you point to only\r
+modifies the config file, not any of the code itself).  But the recent\r
+crypto support uses the gmime 2.4 crypto API, which apparently has\r
+changed in versions of gmime >2.4.\r
+\r
+If you don't have access to gmime 2.4, then maybe you could look into\r
+providing patches for gmime 2.6 support, or alternately into disabling\r
+the notmuch functionality that does not work with gmime 2.6 if only 2.6\r
+is available.\r
+\r
+jamie.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJN5m70AAoJEO00zqvie6q87oIP/jtEx4mh4bcKd5drku+KdHjJ\r
+wyIHw1HLbmNx3GXKLHI8ouFXi+pGC4l5pzztI915GxFZSoDA8nuHvdMbGP7NVs25\r
+PAuLVULan99kVJ7Nfkelmaxf+GNvhHnDmrUdTODKrulRm2Eb9UWt28xgA4x8oBkX\r
+JWEFuXBJlcjClDJVLpf+K6yLwuxlrruLy3TKu20ptBZsLsib8PoNmLzqsKB6kl8J\r
+jphWrNWWULgSRUNlPwpial+jzjRfgZkc2Gri6PCILrJyU3fVvP8+Hg0p/m78b2c6\r
+ix22r9Fbs4Rm38QDj4IbLdchK6UkeAIQuc6YyTVhG3Sz2afQJ4/dDBeOzPHn+IIR\r
+Vyzg9VOpIOcG5rSsUW1l4vgXq/BTsu23WoqZCqoGZ/Hv0q6oNzLq0Gvf82WkLjTr\r
+9+UiUlGXGPfYvvpV1tAllD+KnyL17F5UZ0oxK6/mtq7JJlpIcTB7tmfVPZEuC2PZ\r
+cJTfgztdNWG0oFNSvfAkO103E7wcMDuamOr2xd3SPydfGbV99zrO+3UjeORc1HfS\r
+zKte8vWC7L4gpT/FCSr849zIKkY0HvGRGY4gUArd2qMn1S3rNKbB+i/yEjJrOMUG\r
+rX/0BUmr5YNVup67rA1YwTbJJwoDlJTdjGcn46CVg9derF4+cHpVSl+Rb1NVLOGS\r
+wpnvdAriMCSxKjXInaaD\r
+=162c\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r