On Fri, Sep 2, 2011 at 10:13 AM, Tibs <[email protected]> wrote: > > > 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 > <snip log spew>
> > 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 guessed correctly. What's happening is that you're providing incorrect authentication to the server and it's telling you so, but then git decides that it should fall back to the older (unsupported by us) protocol. I think upgrading your git client might give you better behavior in this regard, but I'm not sure. In any case, make sure the password you're providing is correct according to what's shown at https://code.google.com/hosting/settings - the likelihood is that you're providing the wrong password. > > -- > 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. > > -- 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.
