Guy C. Heckman wrote:
> First off, I'm a noob. Just started using SVN yesterday. I did my initial
> work in cygwin SVN with no problem.
I suggest you try with the official windows SVN client first. The cygwin
SVN client isn't officially supported and might behave sometimes not as
it should.
> I decided to try out TSVN and ever since then I've been pulling my hair out
> trying to figure out why I keep getting this error.
That error is thrown by the subversion library, not by TSVN. It
basically means that you haven't set up the tunnel agent correctly.
> I've been over the SSH FAQ dozens of times checking and rechecking my
> settings. I've also dug through the archive with no luck.
If you try to implement your own tunnel, I suggest you have a look at
the Subversion book: http://svnbook.red-bean.com/
> The only thing I can think of is that the protocol name is throwing TSVN
> off, it is a shared server and instead of running svn+ssh protocol, the
> server is running it as svn+XXssh on port 2222. I have made the entries in
> the Subversion config file (XXssh = $XXssh ssh -p 2222). I created a keyset,
> and sucessfully was able to connect to the ssh with PuTTY using the private
> key. I can run pageant and sucessfully connect without password.
As long as your setup isn't proofed to be correct, don't use
TortoisePlink! TortoisePlink can't show you error messages thrown by the
server because it avoids the console window from showing up (and that's
where those errors would go).
> I also have tried leaving the external ssh client blank in the settings,
> I've tried TortoisePlink both with and without the -l <username> argument.
> I've tried just plink, and even the venerable SSH Shell Client, all with no
> luck.
>
> The Administrator was over today and we ran debug on the server while I
> tried to connect to svn+XXssh://username@your.domain.here/Repo/trunk/ via
> TSVN and there was no communication with the server when I tried to open
> RepoBrowser.
>
> I'm thinking that the protocol might be the problem. Any ideas?
Honestly, I've never used svn+ssh:// myself, so I can't really help you
here. I can only give you the advice to first try the Subversion CL
client - if it doesn't work with that, you can go to the Subversion
mailing list with your problem: there are more guys there which might be
able to help you, because
1. many users there use Linux and svn+ssh
2. The Subversion devs might be able to help you because you're using
your own tunnel agent - since they're the ones who implemented the whole
thing, they might know what you have to do...
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Oct 1 14:09:21 2005