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

RE: Issues with 0.9.33

From: Alexander Kitaev <alex_at_tmate.org>
Date: 2005-08-27 22:24:33 CEST

Hello Roberto,

Thanks for detailed description of the problem.

> eclipse -vmargs -Djavasvn.ssh2.key=/home/sanchezr/.ssh/id_dsa
> \ -Djavasvn.ssh2.username=roberto
As you're using system properties, try commenting out "ssh = ssh ..." line
in Subversion config file, that you may find at ~/.subversion/config, also
please delete ~/.subversion/auth/svn.ssh directory that may contain wrong
cached credentials and try to access your repository with key auth again.

I think there could be bug that reveals itself when both configuration file
and system properties are used to define credentials. I will investigate
this problem next week.

Alexander Kitaev.

> -----Original Message-----
> From: Roberto C. Sanchez [mailto:roberto@familiasanchez.net]
> Sent: Saturday, August 27, 2005 9:53 PM
> To: users@subclipse.tigris.org
> Subject: Re: Issues with 0.9.33
> On Sat, Aug 27, 2005 at 03:25:33PM -0400, Mark Phippard wrote:
> > The best thing would be to focus on getting your
> installation correct.
> > Forget the command line adapter, there are too many parts not
> > implemented. I would focus on JavaSVN and getting it to
> work with your
> > SSH setup. Tell us what you are trying to do and what you
> are seeing.
> >
> > The other option is to use JavaHL. Whether you are using JavaHL or
> > the CLI, you *must* have the 1.2.x version of the
> libraries. I would
> > suggest either 1.2.0 or 1.2.3. Our FAQ points to a site that had
> > Debian packages available.
> >
> OK. It sounds like JavaSVN is the best way to go.
> > In general, it shouldn't matter if your server is running 1.1.4.
> >
> OK. I thought I would just include as much detail as possible.
> > So stick with 0.9.33 and either lets get JavaSVN working or
> make sure
> > you have a correct JavaHL installed.
> >
> OK. I started by upgrading 0.9.30 to 0.9.33 using the
> Eclipse update manger. I then restarted eclipse and went
> into Preferences -> Team -> SVN and set it to JavaSVN. I
> restarted eclipse with this command line:
> eclipse -vmargs -Djavasvn.ssh2.key=/home/sanchezr/.ssh/id_dsa
> \ -Djavasvn.ssh2.username=roberto
> I then went into the SVN Repository Exploring Perspective. I
> went into the add repository dialog and specified the
> repository, including my username and @ before the hostname.
> I left the passwork field blank and received "svn:
> Authentication cancelled" for an error in the console. The
> dialog that popped up said: 'Error validating location:
> "org.tigris.subversion.javahl.ClientException: svn:
> Authentication cancelled"'. It asked me if I wanted to keep
> the location. I said no and was returned to the add
> repository dialog. The server also showed that the ssh
> authentication was password and not key authentication, even
> though I passed in the location of my key on the command line.
> I then entered my password and was able to add the
> repository. I found an Eclipse Java project to checkout and
> selected "Checkout As Project" on the trunk folder of that
> project. When I switched to the Java perspective, the
> project was build and I was able to run it.
> I guess the problem with not being able to access the
> resources has to do with using the command line driver. That
> being the case, I would like to get JavaSVN working, but I
> need key authentication for some of my projects, as that
> particular sever does not allow password authentication.
> Thanks for the quick response and hopefully we can get this
> working. I am especially interested to know why my
> specification of the key file is not honored by Subclipse. I
> think that may be the source of the problem.
> -Roberto
> --
> Roberto C. Sanchez
> http://familiasanchez.net/~roberto
Received on Sun Aug 28 06:24:33 2005

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.