compile error of current git on F15

2011-11-25 Thread Darren McGuicken
On Fri, 25 Nov 2011 13:43:35 -0500, David Bremner wrote: > Just confirm, all the crypto tests pass with this patch? In that case, > can we have the patch (preferably as generated by git-send-email)? Or > did I miss it somewhere in this thread? I don't believe the patch ever made it to the list,

compile error of current git on F15

2011-11-25 Thread David Bremner
On Thu, 24 Nov 2011 21:45:20 +, Darren McGuicken wrote: > Hi guys, I assume this is old news, although I haven't seen anything > else mentioned on list since the chain Dirk started - there's a koji > build of 0.9 for rawhide, the source rpm of which contains a gmime 2.6 > patch. I recently

Re: compile error of current git on F15

2011-11-25 Thread David Bremner
On Thu, 24 Nov 2011 21:45:20 +, Darren McGuicken mailing-notm...@fernseed.info wrote: Hi guys, I assume this is old news, although I haven't seen anything else mentioned on list since the chain Dirk started - there's a koji build of 0.9 for rawhide, the source rpm of which contains a gmime

compile error of current git on F15

2011-11-24 Thread Darren McGuicken
On Wed, 01 Jun 2011 09:55:16 -0700, Jameson Graef Rollins wrote: > On Wed, 01 Jun 2011 05:35:29 -0700, Dirk Hohndel > wrote: > > This used to work and used to be supported and was broken in a > > recent notmuch patch. > > If you don't have access to gmime 2.4, then maybe you could look into >

Re: compile error of current git on F15

2011-11-24 Thread Darren McGuicken
On Wed, 01 Jun 2011 09:55:16 -0700, Jameson Graef Rollins jroll...@finestructure.net wrote: On Wed, 01 Jun 2011 05:35:29 -0700, Dirk Hohndel hohn...@infradead.org wrote: This used to work and used to be supported and was broken in a recent notmuch patch. If you don't have access to gmime

Fwd: Re: compile error of current git on F15

2011-06-02 Thread Daniel Kahn Gillmor
I got the following response off-list from the gmime lead, which he's ok with my re-posting here: On 06/02/2011 08:53 AM, Jeffrey Stedfast wrote: > I don't know why Fedora 15 ships 2.5.x, that seems like a really silly > thing to do. I think I recall the Balsa guys bringing this up in the > past

Re: Fwd: Re: compile error of current git on F15

2011-06-02 Thread Daniel Kahn Gillmor
I got the following response off-list from the gmime lead, which he's ok with my re-posting here: On 06/02/2011 08:53 AM, Jeffrey Stedfast wrote: I don't know why Fedora 15 ships 2.5.x, that seems like a really silly thing to do. I think I recall the Balsa guys bringing this up in the past and

compile error of current git on F15

2011-06-01 Thread Jameson Graef Rollins
On Wed, 01 Jun 2011 05:35:29 -0700, Dirk Hohndel wrote: > This used to work and used to be supported and was broken in a recent > notmuch patch. Hey, Dirk. I would actually say that support for gmime 2.6 was merely coincidental up until now. For all functionality we had been using, the API in

compile error of current git on F15

2011-06-01 Thread Dirk Hohndel
On Tue, 31 May 2011 12:29:28 -0400, Daniel Kahn Gillmor wrote: Non-text part: multipart/signed > i'm CC'ing the upstream lead developer of gmime here to see if he has > any thoughts (and can correct any misrepresentations from me) -- Hi Jeffrey! > > On 05/30/2011 02:43 PM, Jameson Graef Rollins

Re: compile error of current git on F15

2011-06-01 Thread Dirk Hohndel
On Tue, 31 May 2011 12:29:28 -0400, Daniel Kahn Gillmor d...@fifthhorseman.net wrote: Non-text part: multipart/signed i'm CC'ing the upstream lead developer of gmime here to see if he has any thoughts (and can correct any misrepresentations from me) -- Hi Jeffrey! On 05/30/2011 02:43 PM,

Re: compile error of current git on F15

2011-06-01 Thread Jameson Graef Rollins
On Wed, 01 Jun 2011 05:35:29 -0700, Dirk Hohndel hohn...@infradead.org wrote: This used to work and used to be supported and was broken in a recent notmuch patch. Hey, Dirk. I would actually say that support for gmime 2.6 was merely coincidental up until now. For all functionality we had been

compile error of current git on F15

2011-05-31 Thread Daniel Kahn Gillmor
i'm CC'ing the upstream lead developer of gmime here to see if he has any thoughts (and can correct any misrepresentations from me) -- Hi Jeffrey! On 05/30/2011 02:43 PM, Jameson Graef Rollins wrote: > On Sun, 29 May 2011 11:44:05 -0700, Dirk Hohndel > wrote: >> CC -O2 notmuch-reply.o >>

Re: compile error of current git on F15

2011-05-31 Thread Daniel Kahn Gillmor
i'm CC'ing the upstream lead developer of gmime here to see if he has any thoughts (and can correct any misrepresentations from me) -- Hi Jeffrey! On 05/30/2011 02:43 PM, Jameson Graef Rollins wrote: On Sun, 29 May 2011 11:44:05 -0700, Dirk Hohndel hohn...@infradead.org wrote: CC -O2

compile error of current git on F15

2011-05-30 Thread Jameson Graef Rollins
On Sun, 29 May 2011 11:44:05 -0700, Dirk Hohndel wrote: > CC -O2 notmuch-reply.o > notmuch-reply.c: In function ?notmuch_reply_command?: > notmuch-reply.c:658:3: error: unknown type name ?GMimeSession? > notmuch-reply.c:659:3: warning: passing argument 1 of > ?g_mime_gpg_context_new? from

compile error of current git on F15

2011-05-30 Thread Dirk Hohndel
CC -O2 notmuch-reply.o notmuch-reply.c: In function ‘notmuch_reply_command’: notmuch-reply.c:658:3: error: unknown type name ‘GMimeSession’ notmuch-reply.c:659:3: warning: passing argument 1 of ‘g_mime_gpg_context_new’ from incompatible pointer type [enabled by default]

Re: compile error of current git on F15

2011-05-30 Thread Jameson Graef Rollins
On Sun, 29 May 2011 11:44:05 -0700, Dirk Hohndel hohn...@infradead.org wrote: CC -O2 notmuch-reply.o notmuch-reply.c: In function ‘notmuch_reply_command’: notmuch-reply.c:658:3: error: unknown type name ‘GMimeSession’ notmuch-reply.c:659:3: warning: passing argument 1 of

compile error of current git on F15

2011-05-29 Thread Dirk Hohndel
CC -O2 notmuch-reply.o notmuch-reply.c: In function ?notmuch_reply_command?: notmuch-reply.c:658:3: error: unknown type name ?GMimeSession? notmuch-reply.c:659:3: warning: passing argument 1 of ?g_mime_gpg_context_new? from incompatible pointer type [enabled by default]