Username for git.sl.o: <a href="mailto:georgejhunt@gmail.com" target="_blank">georgejhunt@gmail.com</a> projects: pydebug and xophoto The push to jita.sl.o was successful! George <div class="gmail_quote"> On Wed, Nov 3, 2010 at 8:21 AM, Aleksey Lim <<a href="mailto:alsroot@member.fsf.org" target="_blank">alsroot@member.fsf.org</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>On Wed, Nov 03, 2010 at 06:22:14AM -0400, George Hunt wrote: > I tried the push from another ip address. Same result, so it's probably not > the blacklist problem. > > The literature suggests that I should check for world or group writeability > on the path from root to .ssh/known_hosts on the server, and on the client > machine. I have double checked my client. Don't have shell access to server. </div>Could you try to push to the new [testing] gitorious <a href="http://jita.sugarlabs.org/" target="_blank">http://jita.sugarlabs.org/</a> To login to jita.sl.o, you need to use your git login name and wiki password for the same login (if there is no wiki account, follow "Create an account" link to create one) or, if you used OpenID, just login via "OpenID" link on jita. And what is your login on git.sl.o and project you are trying to push? <div><div></div><div> > George > > On Sun, Oct 31, 2010 at 10:30 AM, Aleksey Lim <<a href="mailto:alsroot@member.fsf.org" target="_blank">alsroot@member.fsf.org</a>>wrote: > > > On Sat, Oct 30, 2010 at 07:58:00PM -0400, George Hunt wrote: > > > Hi Aleksey, > > > > > > Thanks for the response. > > > > > > The ssh step fails. Trying ssh -vvv gitorious@git.sugarlabs.orgindicates > > > that the negotiation proceeds in what looks to be a normal manner, until > > the > > > point where the client determines that public key method is authorized, > > and > > > client is offering my public key, and the next response is "connection > > > closed". > > > > > > <snip> > > > debug1: Next authentication method: publickey > > > debug1: Offering public key: > > > debug3: send_pubkey_test > > > debug2: we sent a publickey packet, wait for reply > > > Connection closed by 140.211.167.221 > > > </snip> > > > > "Connection closed" seems suspiciously. We had problem w/ blacklisting > > of some IPs. > > > > Can you try to ssh connect from different IP? > > > > (I'm CCing it to systems@) > > > > > I guessed that the server has forgotten my public key, so I uploaded it > > > again. I don't know if it is related, but the listserve forgot that I was > > > receiving the "digest" form of the list on Oct 16 or so. > > > > > > After the upload still no luck -- though there may be some form of > > > authorization required and/or delay built in, since when I first uploaded > > my > > > public key last year, it didn't work for at least a day. > > > > > > George > > > > > > On Sat, Oct 30, 2010 at 5:53 PM, Aleksey Lim <<a href="mailto:alsroot@member.fsf.org" target="_blank">alsroot@member.fsf.org</a>> > > wrote: > > > > > > > On Sat, Oct 30, 2010 at 05:34:34PM -0400, George Hunt wrote: > > > > > I have 2 projects that I have been pushing git commits to for almost > > a > > > > > year. In one I created a new branch, and was concerned that my local > > > > change > > > > > was preventing the successful "git push". But the other project has > > no > > > > > structural changes, and still gets the response "fatal: the remote > > end > > > > hung > > > > > up unexpectedly" -- which I see has been a source of lots of > > headaches > > > > for > > > > > the inner circle. > > > > > > > > > > Should I just wait for 6 hours, and try again? How to proceed? > > > > > > > > Check if: > > > > > > > > * `ssh <a href="mailto:gitorious@git.sugarlabs.org" target="_blank">gitorious@git.sugarlabs.org</a>` outputs "PTY allocation request.." > > > > * `git config remote.origin.url` output is equal to particular push > > link > > > > on your project web page on git.sl.o > > > > > > > > -- > > > > Aleksey > > > > > > > > -- > > Aleksey > > </div></div>-- Aleksey </blockquote></div>