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

[Subclipse-users] cannot check out due to infinite "getting remote project" message box

From: Chipalo Street <comphw_at_hotmail.com>
Date: 2007-08-01 20:02:31 CEST

Hi, I've been trying to set up an svn+ssh connection for a week now. Fixing
the errors has been slow, but up until now I seem to have been making
progress. First some basic info.

SVN server: debian box with ssh set up
SVN client: Windows Vista
                Eclipse 3.3
                Subclipse 1.2.3 using SVNKit(Pure Java)

For a long time, I was not even able to explore my repository. I having
problems because I was providing my putty key, the one I use to ssh into the
debian box, as the private key when prompted by Subclipse. This key is in
Putty form and, not a OpenSSH2 key as required by Subclipse, so I created a
new OpenSSH2 DSA key, appended the public key to my authorized_keys file,
and began providing Sublipse the new OpenSSH2 DSA private key (with
passphrase). Now I am able to start up Eclipse, add the repository, and
explore the repository (open folders and traverse the SVN tree). The
problem is that I can not check out this project. Here is what happens. I
choose the repositry I want to check out from. It tries connecting, and then
pops up a box asking for the author name to use for the repository. I enter
it and hit OK. It connects to the repository. I choose the folder that I
wish to checkout, and when I hit NEXT or FINISH another box that says
"Getting remote project info" pops up. This box just sits there forever,
and while it's there you can't do anything with Eclipse.

I have looked for similar problems but they seem to be related to SSH
authentication. I don't think that this is my problem because I can explore
the repository just fine. I have also told subclipse to save my private key
and passhphrase and that seems to be fine because when I start Eclipse I
don't have to enter that information anymore, but if I delete the .keyring
file I have to reenter it. I don't think that the problem is the wrong type
of SSH key because, as mentioned before, I made a new one that should be
compatible with subclipse. The debin box is configured correctly because
it's maintained by my school. I've had no problems with ssh in the past, and
others have successfully set up svn+ssh on the same sever (none of them are
around to talk to right now).

I would really appreciate it if someone could give me an answer or at least
give me some ideas abut what might be wrong and how to trouble shoot them.
Thanks soooo much.

Chipalo

_________________________________________________________________
Local listings, incredible imagery, and driving directions - all in one
place! http://maps.live.com/?wip=69&FORM=MGAC01

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Aug 1 20:22:47 2007

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