On Fri, 2004-07-23 at 17:32, Peter Koellner wrote:
> On Fri, 23 Jul 2004, Ben Collins-Sussman wrote:
> > Can you be more specific? Show us a transcript?
> what transcript? it either says "Connection closed unexpectedly"
> or "svn: Das System Kann den angegebenen Pfad nicht finden"
> as typical for windows, this error message does not state what part could
> not find which path...
> or it simply hangs...
> > When you use 'svn+ssh://', the svn client launches an 'ssh' program to
> > execute a remote svnserve process on the server. Unix almost always has
> > an ssh program in $PATH. That's not true in Windows. You need to get
> > yourself an 'ssh.exe' program of some sort.
> err.... i do have cygwin installed, and tried putty/plink too.
> i did set SVN_SSH to something looking useful, and entered host/user config
> into .ssh/config. normal ssh connections do work, and svn: protocol works
It would be nice if you had given us these details the first time. :-)
Plink doesn't work, I'm told. Is 'ssh' in your %PATH%? Show us the
value of %SVN_SSH%
> i'll try that. the thing is - if i got such serious problems with the setup
> myself, i couldn't recommend an installation to my customers at this point.
> since it can't really be that difficult to connect to the server, i need a
> solution that will work within five minutes after reading the documentation,
> so people can read the test installation proposal email, install the client,
> and try it out while continuing to concentrating on their work.
It's not difficult to connect to the server. Please don't judge
subversion badly because one particular method doesn't automatically
work on windows with zero effort. You've chosen the most complex method
of connecting, on the one operating system where it's hardest to get it
svn+ssh:// is only one of four ways to connect to a server: you can use
http://, https://, or just plain old svn://. And none of those methods
require using an external program like 'ssh'.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Jul 24 00:40:54 2004