Re: svn://anonscm.debian.org inaccessible
Tunneling 3690 through my home machine worked and wasn't too slow (8 minutes).
Now that I've got to the git stage I'm having access problems there too.
The first project, di-autobuild seemed to work OK (uses https, judging
by .git/config), but the next couple didn't:
mr checkout: /usr/local/src/debian-boot/debian-installer/installer
Cloning into 'installer'...
fatal: unable to connect to git.debian.org:
moszumanska.debian.org[0: 184.108.40.206]: errno=Connection timed out
moszumanska.debian.org[1: 2001:41c8:1000:21::21:21]: errno=Network is
This is a little odd since I think I've used git and mercurial
successfully from inside the firewall. Maybe git via https is OK, but
via the git protocol it's blocked.
Any ideas? The port forwarding is trickier here because I don't
directly control the URL being used to fetch the repo.
So if I get the network admin to allow 3690 for svn and 9418 for git
will everything just work?
On Sun, Oct 5, 2014 at 5:26 PM, Ross Boylan
> $ date; time svn co svn://anonscm.debian.org/svn/d-i/trunk debian-installer
> Sun Oct 5 16:43:12 PDT 2014
> svn: Can't connect to host 'anonscm.debian.org': Connection timed out
> $ date; time svn co http://anonscm.debian.org/svn/d-i/trunk debian-installer
> Sun Oct 5 16:52:46 PDT 2014
> svn: OPTIONS of 'http://anonscm.debian.org/svn/d-i/trunk': 200 OK
> #but no files
> # same with https
> I presume the culprit is a firewall, but the keepers of the firewall
> are not very responsive to change requests.
> I do not have an account on the the server and so can't ssh.
> Is there an alternative?
> The only system I can access outside the firewall is my home machine
> (from which the first line works fine); maybe I could tunnel 3690
> through it? Even if it works the connection will be very slow.
> Ross Boylan