On Sun, 2005-09-11 at 20:50 -0300, Paulo J. S. Silva wrote:
> I have SubEclipse+JavaSVN on two machines. In both machines I get the
> password dialogue mentioned by Russel in his e-mail. I give my username
> and password but the process fails with the same
As far as I am concerned (using private key rather than login/password
access control) if this dialogue appears at all it's a failure. I never
bother filling those details in.
> org.tigris.subversion.javahl.ClientException: svn: Authentication
> cancelled.
>
> message. I have checked my ssh/subversion server logs and there is no
> sign of a login try. I looks like subeclipse is not even trying to log
> using the give username and password.
From what has happened over the last day or two I would guess JavaSVN is
running but failing to find the private key file and so crashing out
before any SSH connection attempt. I bet starting with the command
line:
eclipse -vmargs -Djavasvn.ssh2.key=<path-to-key-file>
fixes things exactly as they did for me -- though you may need
additional parameter values if you don't use ssh-agent.
> Earlier today Brent Vernet commented that he had fixed this issue, but
> in a private communication he told he fixed it moving to javahl instead
> of JavaSVN. I use Ubuntu Linux and javahl is not a real option right
> now.
>
> For now, I am using a workaround to use subeclipse. I set my repository
> to svn://localhost/path-to-repository in the client machine (note the
> lack of ssh, it is local svn protocol). I then tunnel the connections to
> svnserve using the following command in my shell:
>
> ssh -L 3690:myserver.mydomain:3690 myserver.mydomain svnserve -t
>
> Shouldn't JavaSVN be able do connect using svn+ssh?
I am using Debian Testing rather than Ubuntu (I will have to get this
all running on Ubuntu but not for a few weeks yet) but they are fairly
similar :-)
I have never had to do any hacking of this sort to get things working.
The svn+ssh protocol has always worked fine for me once it connects at
all. In my Gnome session I start an ssh-agent and to the
gnome-ssh-askpass thing. Once Eclipse / Subclipse knows the location of
the private key directory (obviously Subclipse does not use the default
of ~/.ssh/id_dsa for some reason) then everything seems to work fine.
The SSH conenction is made, the key is used via ssh-agent and then the
svn actions happen.
Certainly I would never put up with the workaround you found -- actually
I would never have thought of doing anything so byzantine ;-)
--
Russel.
====================================================
Dr Russel Winder +44 20 7585 2200
41 Buckmaster Road +44 7770 465 077
London SW11 1EN, UK russel@russel.org.uk
Received on Mon Sep 12 20:58:14 2005