[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn+ssh issues on Windows due to passing -q by default

From: Magnus Torfason <zulutime.net_at_gmail.com>
Date: Thu, 11 Feb 2010 13:19:11 -0500

Hi, I sent an email a while ago detailing problems with connecting from
a Windows client to a *nix server over ssh:

On 1/11/2010 5:20 PM, Daniel Shahaf wrote:
> Magnus Torfason wrote on Mon, 11 Jan 2010 at 11:53 -0500:
>> 1: svnsync (through SSVN):
>> A svnsync process from an external server that had always worked did no
>> longer complete successfully. The error message was:
>> plink: unknown option "-q"
>> Connection terminated
> We added the '-q' to the default value of the 'ssh' svn+*:// scheme some
> time ago. The help now reads:
> ...
> Related?
> Daniel
> (my configuration overrides it as follows:
> ssh = $SVN_SSH /path/to/plink.exe -batch -ssh -2
> )

Yes, related.

After more testing it seems clear that this has to do with SlikSvn
distributing an ssh.exe that does not accept the -q switch, but with the
default setting being to pass the -q.

TortoiseSVN ships with its own version of plink, and does not suffer
from this issue (but copying that version over does not seem to fix it
for me).

Changing the config file to read
ssh = $SVN_SSH ssh
fixes this issue for me, but it means that TortoiseSVN also uses the
SlikSvn plink, which is not really what I want. It seems to me that the
best solution would be to change the behavior in the SlikSvn
distribution for Windows, either by removing the -q from the default
settings, or by patching the plink (named ssh.exe and presumably
custom-built) that ships with SlikSvn.exe so that it will ignore the -q
switch rather than throw an error.

Received on 2010-02-11 19:19:50 CET

This is an archived mail posted to the Subversion Dev mailing list.