GNOME Bugzilla – Bug 650337
Cannot upload release
Last modified: 2011-05-17 03:04:08 UTC
I am trying to upload a new release of glabels. The last time I did this was back in January. I know there have been changes to the infrastructure since then, but I have not been able to find any updated directions. When I do an scp or ssh to master.gnome.org, it just sits there for several minutes until I get a Connection closed by 209.132.180.178 Here is the verbose output from ssh: $ ssh -v jimevins@master.gnome.org OpenSSH_5.5p1 Debian-4ubuntu5, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to master.gnome.org [209.132.180.178] port 22. debug1: Connection established. debug1: identity file /home/evins/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /home/evins/.ssh/id_rsa-cert type -1 debug1: identity file /home/evins/.ssh/id_dsa type -1 debug1: identity file /home/evins/.ssh/id_dsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.5p1 Debian-4ubuntu5 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'master.gnome.org' is known and matches the RSA host key. debug1: Found key in /home/evins/.ssh/known_hosts:12 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received Connection closed by 209.132.180.178 Is there a new procedure that I am not aware of, or is something else wrong?
I tried again this evening and everything worked perfectly.