views:

1289

answers:

4
A: 

If subversion is not included in your SVN plugin, then you need to upgrade your svn client itself. Have you checked whether the server you're connecting with has not been updated?

Keltia
+1  A: 

You can try to set SVN plugin (subclipse?) to use svnkit instead of native client.

Dev er dev
+3  A: 

At some point, someone ran a SVN comment on your sandbox using a client that uses a newer fromat than your plugin (probably a Subversion 1.5 client where you had previously been using 1.4).

If you don't update your client/plugin, you can checkout your sandbox again using your preferred client/plugin, or use the change-svn-wc-format.py script, as detailed in the Subversion 1.5 release notes, under Working Copy and Repository Format Changes.

Blair Conrad
The python script fixed this issue for me. Except my problem was caused by mixing Tortoise and command-line SVN.
User1
+2  A: 

Subversion clients automatically upgrade your working copy when they touch it. As Blair said something has touched your working copy with probably a 1.5 client.

You need to keep all your different Subversion clients - CollabNet (command-line), TortoiseSVN, Subclipse, Subversive, etc. - all on the same minor version (1.4 vs. 1.5), or you'll continue to have this problem.

Blair's got a good strategy for a fix, but the easiest thing to do would be to re-checkout the working copy.

John Stoneham