On Thu, Feb 07, 2008 at 10:15:02AM +0000, Anand Kumria wrote: > > OK, I was finally able to reproduce your bug. It seems that it _only_ > > happens when using curl built against gnutls. I built against the > > libcurl4-openssl-dev in Debian unstable, and the problem goes away. > > Thanks for figuring out how to reproduce it ... how did you btw? I saw the gnutls error message in your output and took a guess that it was related. I was able to reproduce against the first https repository that I tried (I don't think it has anything to do with the repository). I wish we could more certainly blame it on something besides git, though. I can't reproduce it using just 'curl', so it's possible that there is a problem with the way git is calling libcurl. > 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). > > I agree with you, it is a bit problematic when the library (curl) relies > on another library (gnutls) and the bottom one is having a problem. It would be nice if we could generate a minimal test case that demonstrates the problem, but I can't seem to reproduce it with a smaller program. If we could, then we could probably get advice from curl and/or gnutls people. -Peff - 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
