git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-fetch in 1.5.4 fails versus 1.5.3.8

From
AKAnand Kumria <wildfire@progsoc.org>
Date
Feb 8, 2008, 02:43 UTC
Message-ID
<pan.2008.02.08.02.43.21@progsoc.org>
In-Reply-To
<20080207232337.GR30368@dpotapov.dyndns.org>
On Fri, 08 Feb 2008 02:23:37 +0300, Dmitry Potapov wrote:
Show 17 quoted lines
> 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
Previous: Dmitry PotapovNext: Dmitry Potapov
Message 43 of 44 in “git-fetch in 1.5.4 fails versus 1.5.3.8”
  1. Anand KumriaFeb 4, 2008
  2. Jeff KingFeb 5, 2008
  3. Jari AaltoFeb 5, 2008
  4. Anand KumriaFeb 6, 2008
  5. Jeff KingFeb 7, 2008
  6. Mike HommeyFeb 7, 2008
  7. Anand KumriaFeb 7, 2008
  8. Jeff KingFeb 7, 2008
  9. Mike HommeyFeb 7, 2008
  10. Jeff KingFeb 7, 2008
  11. Mike HommeyFeb 7, 2008
  12. Jeff KingFeb 8, 2008
  13. Mike HommeyFeb 8, 2008
  14. Mike HommeyFeb 8, 2008
  15. Work around curl-gnutls not liking to be reinitializedMike Hommey, Feb 8, 2008
  16. Mike HommeyFeb 8, 2008
  17. Junio C HamanoFeb 8, 2008
  18. Mike HommeyFeb 8, 2008
  19. Mike HommeyFeb 8, 2008
  20. Work around curl-gnutls not liking to be reinitializedMike Hommey, Feb 8, 2008
  21. Johannes SchindelinFeb 8, 2008
  22. Work around curl-gnutls not liking to be reinitializedMike Hommey, Feb 8, 2008
  23. Mike HommeyFeb 8, 2008
  24. Work around curl-gnutls not liking to be reinitializedMike Hommey, Feb 9, 2008
  25. Daniel StenbergFeb 9, 2008
  26. Florian WeimerFeb 9, 2008
  27. Mike HommeyFeb 9, 2008
  28. Johannes SchindelinFeb 8, 2008
  29. Mike HommeyFeb 8, 2008
  30. Jeff KingFeb 9, 2008
  31. Frank LichtenheldFeb 7, 2008
  32. Linus TorvaldsFeb 7, 2008
  33. Frank LichtenheldFeb 7, 2008
  34. Linus TorvaldsFeb 7, 2008
  35. Anand KumriaFeb 7, 2008
  36. Jeff KingFeb 7, 2008
  37. Linus TorvaldsFeb 7, 2008
  38. Martin LanghoffFeb 7, 2008
  39. Dmitry PotapovFeb 7, 2008
  40. Jeff KingFeb 7, 2008
  41. Jeff KingFeb 7, 2008
  42. Dmitry PotapovFeb 7, 2008
  43. Anand KumriaFeb 8, 2008
  44. Dmitry PotapovFeb 8, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.