I just wanted to note that I stand corrected on the issue below. It
turns out that SlikSvn does not distribute an ssh.exe. I must have put
it there manually and then forgot all about it. So the message really
should have gone to the user list, not the dev list.
Sorry about the noise.
On 2/11/2010 1:19 PM, Magnus Torfason wrote:
> 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:
>> (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-12 16:33:06 CET