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

Re: [Subclipse-users] Client too old error on OS X

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-11-11 16:50:04 CET

Kristian Duske <4815162342n@gmail.com> wrote on 11/11/2006 10:42:24 AM:

> ok, I have searched my entire system for javasvn.jar - nothing. As
> long as it's not contained within another jar in some Eclipse plugin,
> the jar included in the Subclipse core is the only one I have.

You could delete older versions of Subclipse plugins to eliminate that.

> I have tested a few things though:
> Created a new repository on the server and shared a new project into
> that repository - this works.
> Checked out an existing project into Eclipse, changed a file and
> commited - this works too, but the commit operation takes a lot of
> time. Is this normal?
> So the only thing that does not work is commiting a file from an
> existing Eclipse project that is already shared. I guess I can work
> around my problem by checking out all my projects again, copying the
> old files over the checked out files and commit that. This seems to
> indicate that Jerry is indeed right. I don't know Subclipse enough to
> be sure on this.

It would never be expected to get the problem if you only use a single
client. The issue would show up if you touched the same working copy with
another client, such as the 1.4 command line. Before you delete your old
projects, use a 1.4 command line to run the svn update command, and maybe
svn cleanup as well. Then just see if they can then work in Subclipse.
This would test Alex's theory about the 1.3 to 1.4 format update being
incomplete. If those commands work with the command line, then it should
be OK.

> Well, I guess my problem is kinda solved, but what about the long
> running commit operations? Any tips about that?

Are you using svn:// and the server running on a *nix OS? There are some
known scenarios where this can be slow because the server is hung trying
to generate a random number. Has to do with how that process is done and
the only fix is to rebuild APR to use a different source for random
numbers that does not have the problem.


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sat Nov 11 16:50:14 2006

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.