After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 625135 - I can't clone or pull the gtk+ repo
I can't clone or pull the gtk+ repo
Status: VERIFIED NOTGNOME
Product: sysadmin
Classification: Infrastructure
Component: Git
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
: 626164 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-07-23 16:21 UTC by Javier Jardón (IRC: jjardon)
Modified: 2010-08-06 08:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Some mtr statistics (1.84 KB, text/plain)
2010-07-23 17:50 UTC, Javier Jardón (IRC: jjardon)
Details

Description Javier Jardón (IRC: jjardon) 2010-07-23 16:21:42 UTC
I get this:

$ git clone git://git.gnome.org/gtk+
Cloning into gtk+...
fatal: The remote end hung up unexpectedly
Comment 1 Jason Clinton 2010-07-23 16:24:21 UTC
I see the same here.
Comment 2 André Klapper 2010-07-23 16:38:19 UTC
git pull --rebase
just worked fine here.
Comment 3 Jeff Schroeder 2010-07-23 17:09:12 UTC
We've seen this before. Please tell us where you're pulling from (what country / location).

Can you also run "mtr git.gnome.org" for a few minutes to see if you are experiencing any heavy packet loss. If so paste that as well. It just worked fine for me (California, USA).
Comment 4 Javier Jardón (IRC: jjardon) 2010-07-23 17:50:42 UTC
Created attachment 166463 [details]
Some mtr statistics

The connection is from A Coruña, Spain.

There are other people in the same room (all with a wifi connection) and they can clone the repo without problems.
I can clone other modules without problems.
Comment 5 Simos Xenitellis 2010-07-23 18:12:52 UTC
I used to get 'The remote end hung up unexpectedly' when I tried to clone all of the GNOME packages a few times. Can you verify whether there is a mechanism on git.gnome.org that blocks (temporarily?) connections if somehow it thinks that IP address is abusing?
Comment 6 Jeff Schroeder 2010-07-23 20:23:08 UTC
iptables is clean.
Comment 7 Felix Riemann 2010-07-24 13:40:56 UTC
Seems like a bug/behaviour change in recent git versions:

http://thread.gmane.org/gmane.comp.version-control.git/151529
Comment 8 Jeff Schroeder 2010-07-26 14:05:17 UTC
Thanks for digging up the link Felix.

In case gmane is offline and someone wants to know the workaround, the problem was introduced into git via "9d2e942 decode file:// and ssh:// URLs". It is a bug in the way git handles the "+" character in non-query urls.

The workaround is to use an older version of git, or clone:
git://git.gnome.org/gtk%2B

This bug should be fixed eventually in upstream git.
Comment 9 Luca Bruno 2010-07-27 10:05:19 UTC
(In reply to comment #8)
> The workaround is to use an older version of git, or clone:
> git://git.gnome.org/gtk%2B

$ git clone git://git.gnome.org/gtk%2B
Initialized empty Git repository in /home/lethal/gnome2/gtk%2B/.git/
fatal: The remote end hung up unexpectedly

I'm reopening the bug.
Comment 10 Ralf Ebert 2010-08-05 15:49:14 UTC
jhbuild gave me:

*** Checking out gtk+ *** [22/36]
git clone git://git.gnome.org/gtk+
Cloning into gtk+...
fatal: The remote end hung up unexpectedly
*** Error during phase checkout of gtk+: ########## Error running git clone git://git.gnome.org/gtk+ *** [22/36]

tried to check it out manually from git://git.gnome.org/gtk+, got the same error

git clone 'git://git.gnome.org/gtk%2B' worked

git version 1.7.2 on Ubuntu 10.04
Comment 11 Fernando Herrera 2010-08-05 16:01:15 UTC
If you have an already checkout repository and have updated your git client, you can still work with it without cloning a new one with this workaround:
- edit gtk+/git/config
- replace: 
    url = ssh://XXX@git.gnome.org/git/gtk+
  with:
    url = ssh://XXX@git.gnome.org/git/gtk%2B
Comment 12 Tobias Mueller 2010-08-05 16:05:16 UTC
Same for me. The problem is apparently git and I was told that it was fixed in 1.7.2.1. So I propose to close this bug as NOTGNOME. Feel free to revert.

Luca, if "git clone 'git clone 'git://git.gnome.org/gtk%2B'" doesn't work for you, please tell us, which version you are using.
Comment 13 Luca Bruno 2010-08-05 18:48:02 UTC
(In reply to comment #12)
> Same for me. The problem is apparently git and I was told that it was fixed in
> 1.7.2.1. So I propose to close this bug as NOTGNOME. Feel free to revert.
> 
> Luca, if "git clone 'git clone 'git://git.gnome.org/gtk%2B'" doesn't work for
> you, please tell us, which version you are using.

I have git 1.7.1, perhaps I have to wait for debian sid to ship 1.7.2. Thanks.
Comment 14 Ralf Ebert 2010-08-05 21:16:35 UTC
git 1.7.2.1 on the client side doesn't fix this, can you please reopen the bug?

$ git --version
git version 1.7.2.1
$ git clone 'git://git.gnome.org/gtk+'
Cloning into gtk+...
fatal: The remote end hung up unexpectedly
$ git clone 'git://git.gnome.org/gtk%2b'
Cloning into gtk%2b...
remote: Counting objects: 233755, done.
Comment 15 Jeff Schroeder 2010-08-05 21:19:16 UTC
While unfortunate, this is a bug in your git client. There is no reason to re-open this bug.
Comment 16 Christian Rose 2010-08-06 08:31:00 UTC
*** Bug 626164 has been marked as a duplicate of this bug. ***