On Wed, Feb 06, 2008 at 09:56:35PM +0000, Anand Kumria wrote: > With GIT_SSL_NO_VERIFY defined, it fails with: > > $ GIT_SSL_NO_VERIFY=1 ../git/git-fetch richard > error: gnutls_handshake() failed: ASN1 parser: Element was not found. (curl_result = 35, http_code = 0, sha1 = 510567ca41e201253445528ca6eb89ed43e71fce) > Getting pack list for https://server.example.com/~richard/newfoo.git > error: gnutls_handshake() failed: ASN1 parser: Element was not found. > Getting alternates list for https://server.example.com/~richard/newfoo.git > error: Unable to find 510567ca41e201253445528ca6eb89ed43e71fce under https://server.example.com/~richard/newfoo.git > Cannot obtain needed object 510567ca41e201253445528ca6eb89ed43e71fce > fatal: Fetch failed. 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. Can you confirm that building using the openssl version of curl fixes the problem? 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. > I *think* what is happening is that it is it is trying for the object > - not seeing it and then not attempting to get the pack file. No, it only fails to see objects because of the curl failure (it tries the loose and then the pack). -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
