http://threebytesfull.com/2008/04/git-with-and-without-proxy.html
Question about that post?
I'm not able to make it work :(
I'm using cntlm
http://cntlm.awk.cz/
Can you help me to understand what I'm missing!
I think the problem is in relation with my understanding of
my.socks.server:1080 ?? What should I but there?
thx
[kapare@p11634 mydroid]$ cat /usr/local/bin/socks-gw
#!/bin/sh
# Filename: ~/bin/socks-gw
# This script connects to a SOCKS proxy using connect.c
/usr/local/bin/connect -S localhost:1080 $@
[kapare@p11634 mydroid]$ cat /usr/local/bin/socks-ssh
#!/bin/sh
# Filename: ~/bin/socks-ssh
# This script opens an SSH connection through a SOCKS server
ssh -o ProxyCommand="/usr/local/bin/socks-gw %h %p" $@
[kapare@p11634 mydroid]$ $http_proxy
bash:
http://127.0.0.1:3128: No such file or directory
[kapare@p11634 mydroid]$ ls $GIT_SSH
/usr/local/bin/socks-ssh
[kapare@p11634 mydroid]$ ls $GIT_PROXY_COMMAND
/usr/local/bin/socks-gw
[kapare@p11634 mydroid]$ repo init -u git://
android.git.kernel.org/platform/manifest.git
Getting repo ...
from git://
android.kernel.org/tools/repo.git
ERROR: Got error response from SOCKS server: 1 (general SOCKS server
failure).
FATAL: failed to begin relaying via SOCKS.
fatal: The remote end hung up unexpectedly
[kapare@p11634 mydroid]$
On Oct 22, 10:48 am, Chris <
chris.l.elf...@intel.com> wrote:
> David Given wrote:
> > I've finally managed to get a copy of the source;
git.webkit.org was
> > back up, but repo sync would die every couple of minutes, but I just
> > kept repeating it until it worked. However, I don't have the necessary
> > tools to build it yet, so I don't know if it's complete.
>
> The webkit problem got resolved for me when the team switched over to
> mirrors for some external components (seehttp://
source.android.com/known-issues).
>
> From in front of theproxy, I got lucky and had a totally clean "repo
> sync" from in front of theproxywith no socket errors late last
> night. From behind aproxy, I was able to sync successfully sometime
> last night with a "repo sync" in a loop with a 60 second backoff until
> it succeeded. I was definately seeing random socket errors too.
> Hopefully it will get better with updates to the servers, repo tool,
> and after the initial hammering of downloads completes...
>
> Now on to trying to build...
>
> David Given wrote:
> > Chris wrote:
> > > I suspect that you are right and these external components and
> > > associatedgitrepositories are getting hammered. I have yet to see
> > > success getting past
thegit.webkit.org stage of repo sync.