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

Re: [Subclipse-users] Strange Incompatibility behavior

From: Mark Phippard <markphip_at_gmail.com>
Date: 2006-12-13 22:16:35 CET

On 12/13/06, web1_sonic <sonic@www.outcoders.com> wrote:
> I'm using a php framework (cakePHP if you're interested) and try to stay
> up to date with the repository. So I use svn to check out and update the
> code. Within the work I have my 'app' directory. I've recently started to
> try to use Eclipse (actually EasyEclipse) and so use subclipse to checkout a
> working copy of my app into a subdirectory of the Framework.
> I noticed that once I check something out with Subclipse, if I try to use
> the svn CLI on the working copy, I get an error:
> "svn: This client is too old to work with working copy '.'; please get a
> newer Subversion client"
> My svn client is v1.3.2 and my Subclipse is 1.1.8.
> However, once I go back to the parent directory and try to use the svn CLI
> to operate on the framework (which I checked out with the CLI) I get the
> same error, even though I did now use Subclipse to check out the Framework.
> I only used Subclipse to check out the application subdirectory.
> Is this normal behaviour or is this a bug? Is there a work-around for
> this?

This is normal behavior. It comes from Subversion 1.4 (which Subclipse
includes) not Subclipse itself. Your best option is to update your command
line to 1.4.2. The Subversion 1.4 release notes describe what is happening:


Received on Wed Dec 13 22:16:44 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.