diego@BRAIN /c/srcNow, it only happens at home where my ISP is making nice tricks and probably killing everything that is not "http" (note how slow it works, 1kbs to 5kbs). Just to compare, in my workplace with a business contract I can pull at normally (at 100-180kbs).
$ rm -fr qt && time git clone git://gitorious.org/qt/qt.git
Initialized empty Git repository in c:/src/qt/.git/
remote: Counting objects: 218976, done.
remote: Compressing objects: 100% (56957/56957), done.
fatal: The remote end hung up unexpectedly.68 MiB | 5 KiB/s
fatal: early EOF
real 41m40.578s
user 0m0.015s
sys 0m0.000s
Any tricks? I was thinking of using a ppptp connection to work, and then pull from that (or even ssh), but I am sure that there are workarounds for this issue. Yes, I tried http, this is what I get:
diego@BRAIN /c/src
$ rm -fr qt && time git clone http://gitorious.org/qt/qt.git
Initialized empty Git repository in c:/src/qt/.git/
fatal: http://gitorious.org/qt/qt.git/info/refs not found: did you run git updat
e-server-info on the server?
real 0m1.953s
user 0m0.015s
sys 0m0.000s
Any good ideas/workarounds/solutions...?
Posts
5 comments:
Maybe use http protocol instead of git:// ?
Git supports http.
Another way would be to tunnel git through some web proxy. I used to use one that I don't remember the name to bypass my ISP's faulty routers. It involved a socket capture program and an online HTTP proxy. Can't remember what was it :(
Sebastián see my post, I tried http and it did not work.
if you have ssh access to somewhere where it works, just open a socks proxy with -D*port* and then use tsocks to reroute git;
I am actually in the exact same situation as you depicted and I have to run everything (kopete, quasselcore, git, even svn sometimes) thru tsocks. It works (mostly)
--J
The http:// URL is not exactly the same as the git:// URL.
Try
git clone http://git.gitorious.org/qt/qt.git
The subtle change is the "git." part before gitorious.org for http.
Thank you. This worked!
Post a Comment