On Sep 2, 3:33 pm, Augie Fackler <[email protected]> wrote: > Looking at the code and logged error here, this appears to only be > possible if you fall back to non-smart http. I have no idea why your > git client would do that, but can you run 'GIT_CURL_VERBOSE=1 git > push' and see if the log spew provides any useful hints?
OK [tibs@spoon muddle]$ GIT_CURL_VERBOSE=1 git push * About to connect() to code.google.com port 443 (#0) * Trying 74.125.79.102... * Connected to code.google.com (74.125.79.102) port 443 (#0) * found 143 certificates in /etc/ssl/certs/ca-certificates.crt * server certificate verification OK * common name: *.google.com (matched) * server certificate expiration date OK * server certificate activation date OK * certificate public key: RSA * certificate version: #3 * subject: C=US,ST=California,L=Mountain View,O=Google Inc,CN=*.google.com * start date: Fri, 12 Aug 2011 03:49:02 GMT * expire date: Sun, 12 Aug 2012 03:59:02 GMT * issuer: C=US,O=Google Inc,CN=Google Internet Authority * compression: NULL * cipher: ARCFOUR-128 * MAC: SHA1 > GET /p/muddle//info/refs?service=git-receive-pack HTTP/1.1 User-Agent: git/1.7.0.4 Host: code.google.com Accept: */* Pragma: no-cache < HTTP/1.1 401 Unauthorized < WWW-Authenticate: Basic realm="Google Code git Repository" < Content-Type: text/html; charset=UTF-8 < X-Content-Type-Options: nosniff < Date: Fri, 02 Sep 2011 14:50:08 GMT < Server: git_frontend < Content-Length: 11846 < X-XSS-Protection: 1; mode=block < * Ignoring the response-body * Connection #0 to host code.google.com left intact * Issue another request to this URL: 'https://code.google.com/p/ muddle//info/refs?service=git-receive-pack' * Re-using existing connection! (#0) with host code.google.com * Connected to code.google.com (74.125.79.102) port 443 (#0) * Server auth using Basic with user '[email protected]' > GET /p/muddle//info/refs?service=git-receive-pack HTTP/1.1 Authorization: Basic dGlic0B0b255aWJicy5jby51azp4QTZqZzNlbTlhazU= User-Agent: git/1.7.0.4 Host: code.google.com Accept: */* Pragma: no-cache * The requested URL returned error: 403 * Closing connection #0 * About to connect() to code.google.com port 443 (#0) * Trying 74.125.79.102... * Connected to code.google.com (74.125.79.102) port 443 (#0) * found 143 certificates in /etc/ssl/certs/ca-certificates.crt * SSL re-using session ID * server certificate verification OK * common name: *.google.com (matched) * server certificate expiration date OK * server certificate activation date OK * certificate public key: RSA * certificate version: #3 * subject: C=US,ST=California,L=Mountain View,O=Google Inc,CN=*.google.com * start date: Fri, 12 Aug 2011 03:49:02 GMT * expire date: Sun, 12 Aug 2012 03:59:02 GMT * issuer: C=US,O=Google Inc,CN=Google Internet Authority * compression: NULL * cipher: ARCFOUR-128 * MAC: SHA1 * Server auth using Basic with user '[email protected]' > GET /p/muddle//info/refs HTTP/1.1 Authorization: Basic dGlic0B0b255aWJicy5jby51azp4QTZqZzNlbTlhazU= User-Agent: git/1.7.0.4 Host: code.google.com Accept: */* Pragma: no-cache < HTTP/1.1 200 OK < Content-Type: text/plain < Expires: Fri, 01 Jan 1980 00:00:00 GMT < Pragma: no-cache < Cache-Control: no-cache, max-age=0, must-revalidate < Date: Fri, 02 Sep 2011 14:50:10 GMT < Server: git_frontend < Transfer-Encoding: chunked < * GnuTLS recv error (-9): A TLS packet with unexpected length was received. * transfer closed with outstanding read data remaining * Closing connection #0 error: GnuTLS recv error (-9): A TLS packet with unexpected length was received. while accessing https://code.google.com/p/muddle//info/refs fatal: HTTP request failed [tibs@spoon muddle]$ Hmm. Trying to think what else might be useful information. I've got my ~/.netrc set up with permission: ------------------- [tibs@spoon muddle]$ ls -l ~/.netrc -rw-r--r-- 1 tibs tibs 345 2011-07-18 10:07 /home/tibs/.netrc -------------------- and contents (with the passwords, etc., "blacked out"): -------------------------- machine rxxxxxxxx.kynesim.co.uk login XXXXXXX password ############ # Only the first entry for code.google.com will actually be used, # but the other might be of interest at some time machine code.google.com login [email protected] password ############ machine code.google.com login [email protected] password ############ ----------------------- but my ~/.gitconfig has: ------------------------ [user] name = Tony Ibbs email = [email protected] [core] excludesfile = /home/tibs/.gitignore ------------------------ So I guessed the 403 error might be related, and added [email protected] as a google user, added them to the muddle project, and added the appropriate lines to my .netrc. But that doesn't seem to have made a difference (so presumably I was overoptimistic). And I'm afraid I have go for now, so won't be able to respond further until next week. -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
