On Fri, 08 Feb 2008 02:23:37 +0300, Dmitry Potapov wrote: > On Thu, Feb 07, 2008 at 10:15:02AM +0000, Anand Kumria wrote: >> On Wed, 06 Feb 2008 23:23:33 -0500, Jeff King wrote: >> >> > Googling for your error message turns up only one other instance: a >> > bug in pidgin where the result was "this seems like a bug in gnutls." >> > I hate to say "it's not our bug" without knowing exactly what is >> > causing it, though. And it does seem odd that it works with 1.5.3.8. >> > I wonder if there is some difference in the way we are calling curl >> > that matters. >> >> It appears that git 1.5.3.8 on Debian links to libcurl3-gnutls whereas, >> at least for me, git 1.5.4 on Debian links to libcurl4-gnutls (or >> libcurl4-openssl). > > Have you tried Git 1.5.4 with libcurl3-gnutls? It seems the package from > Debian unstable is built with it. I have backported Git 1.5.4 to Etch > with libcurl3-gnutls and I have not noticed any problems with https Yes. I've tried the Debian git 1.5.3.8 and git 1.5.4 with whatever they are linked to (libcurl3-gnutls as you point out). When I decided to build & bisect to see if I could troubleshoot, I ended up building with libcurl4-gnutls-dev installed first. When compiled against libcurl4-openssl-dev things works. So it definately seems specific to how git uses libcurl and how it, in turn, uses gnutls. Anand - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
