This client is too old to work with working copy

Question

Everywhere I go on google I get the same answer to this problem but it is the wrong answer for me. Originally I installed Subversion 1.5.6 for windows (i run Windows Server 2008

Answer 1

I had the same error. But the cause was I checked out the project with a svn 1.5 client and my subclipse plugin in eclipse was version 1.4. So updating my subclipse plugin to 1.6 version did the trick. so the problem was subclipse 1.4 does not work with projects that were checked out with svn 1.5 client.

Hope this helps someone.

Answer 2

You claim that the cause of your problem is not the post-commit hook script but my hunch is that that is exactly the root of your problems. When your post-commit script runs, how does it get the files out of your Subversion server so that it can copy them to your web server? Does it not check them out? Besides, you say that everything was working fine until you installed the post-commit hook script.

I have worked in mixed-mode client/server SVN installation situations before, including TortoiseSVN as a client and I have never come across any incompatibilities as long as the clients that work on the same repository are the same version.

Could you please post the contents of your post-commit hook so we can elaborate further?

Answer 3

If you go from 1.6 down to 1.5 you could need to downgrade. You never tell us how you move your repository but you must depending on how you do that get a version of the repository itself.

http://wiki.open.collab.net/wiki/Subversion_Client_FAQ#head-ed7f8e6b7f3265c74eaf7d49dcd4aab85bae2a12

Answer 4

It turns out my server version of SVN was 1.5.6, but the TortoiseSVN client I had installed on the server was version 1.6.3. When I would checkout my wwwroot working copy (or update it using the right click options TortoiseSVN gave me) and updated that working copy's version, the SVN server couldn't update it because it was a lower version.

I downloaded TortoiseSVN 1.5.6 from file hippo and re-checked out the working copy on the server and it all worked great!

Answer 5

Check to see what svn command your post-commit hook script is running. Check that the version of this command matches the version of the last SVN client to touch your repository.

By default when using a new version of a subversion client it will upgrade the repository to that version. This means that suddenly older clients just stop working.

Answer 6

In my case I moved eclipse code from one place to another then the problem started. For solving I checkout the project form the svn repo. Then in old project I cleaned all svn files. (simply search .svn and delete ) then I copy the content to the just checked out project, my changes became visible and my project is up to date. This method can be applied for other annoying errors. Hope this help someone