Skip Menu |

This queue is for tickets about the svk CPAN distribution.

Report information
The Basics
Id: 37638
Status: new
Priority: 0/
Queue: svk

People
Owner: Nobody in particular
Requestors: trent.bitcard [...] trentonadams.ca
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: v2.0.2
Fixed in: (no value)



Subject: svk commits do not work when offline
I am almost certain that I was able to commit to svk, even when I was offline. But, that functionality has ceased to work. It now REQUIRES that I be on a network with access to my svn server. Where should I start with diagnosing this problem? Thanks.
From: trent.bitcard [...] trentonadams.ca
On Sat Jul 12 12:56:59 2008, Trent wrote: Show quoted text
> I am almost certain that I was able to commit to svk, even when I was > offline. But, that functionality has ceased to work. It now REQUIRES > that I be on a network with access to my svn server. > > Where should I start with diagnosing this problem? > > Thanks.
Oh, saw the message on the new ticket page, just after I clicked submission. - Mac OS X Leopard Darwin Macintosh.local 9.3.0 Darwin Kernel Version 9.3.0: Fri May 23 00:49:16 PDT 2008; root:xnu-1228.5.18~1/RELEASE_I386 i386 - perl 5.8.8 Here's the output of the svk commit command... svk commit pom.xml Waiting for editor... Commit into mirrored path: merging back directly. Merging back to mirror source svn+ssh://svn.mydomain.ca/var/svn/repos. error: Local proxy could not be resolved.: [22] Invalid argument ssh_exchange_identification: Connection closed by remote host Commit message saved in svk-commitICjES.tmp. Network connection closed unexpectedly: Connection closed unexpectedly So, I just realized that it's related to using a "proxy" with SSH. So, here's the SSH configuration. I am using a program called "proxy tunnel". Host *.mydomain.ca ProxyCommand /usr/local/bin/proxytunnel -v -p abda.mydomain.org:80 -d %h:%p -H "User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Win32)\n" ServerAliveInterval 30 So, as you can see, it doesn't work. If I attempt to connect without the proxy tunnel, I get the same return error code from ssh (255). I will try and include more as it is requested.
From: trent.bitcard [...] trentonadams.ca
On Sat Jul 12 13:05:38 2008, Trent wrote: Show quoted text
> On Sat Jul 12 12:56:59 2008, Trent wrote: > If I attempt to connect without > the proxy tunnel, I get the same return error code from ssh (255).
What I mean by the above is not connecting with svk, but using the command line ssh, and then going "echo $?". Just so you're not confused, thinking I have a problem. Also, since I'm at home, I don't need the proxy command, so I just removed it from the ssh config. The svk commits now work.
From: trent.bitcard [...] trentonadams.ca
On Sat Jul 12 13:09:37 2008, Trent wrote: Show quoted text
> On Sat Jul 12 13:05:38 2008, Trent wrote:
> > On Sat Jul 12 12:56:59 2008, Trent wrote:
> Also, since I'm at home, I don't need the proxy command, so I just > removed it from the ssh config. The svk commits now work.
Oops, that's me lying. I was turning the network on and off, and forgot to turn it off before committing. I was connected to the network. Doing it while not connected, does not work, whether I'm using a proxy or not.