Subversion: working copy - old development version

Question

I am developing OSX and one of my working Subversion copies just started returning the following error for all commands, however my other checks work fine. I get the same message with my installed Brew SVN files, as well as with my Cornerstone client, but other working directories are fine.

> svn update svn: E155036: Please see the 'svn upgrade' command svn: E155036: Working copy '/working_directory' is an old development version (format 12); to upgrade it, use a format 18 client, then use 'tools/dev/wc-ng/bump-to-19.py', then use the current client > svn upgrade svn: E155019: Can't upgrade '/working_directory' as it is not a pre-1.7 working copy directory svn: E150000: Missing default entry 

I don't have a bump-to-19.py script anywhere on my computer (according to find / -type f -name bump-to-19.py ), but I think I could find it on the Apache repository . However, I am not familiar with what he is doing, or how to use it. Ideally, I can avoid checking the new version of this working directory and manually merging in all of my (many) changes.

The only information I could find is related to Netbeans and javahl , and I do not use any of them.

EDIT : after downloading the bump-to-19.py file and creating its executable, I tried it against my working directory to no avail:

 > ./bump-to-19.py working_directory/ error: format is 29 not 18: 'working_directory/' 

Answer 1

Although I was not able to find out why my working directory was damaged, I managed to get around it with rsync - there is a C option that will ignore CVS / SVN files and directories when creating a backup. I made a backup using this option, checked the project again and copied the backup to a new working directory. SVN is happy again.

 > rsync -arC working_directory working_directory_no_svn > rm -rf working_directory > svn co https://svn.example.com/project/trunk working_directory > rsync -ar working_directory_no_svn working_directory 

Answer 2

I had the same problem, and here is how I solved it:

• Delete the top level .svn folder (rm -rf.svn)
• Check the SVN software again (svn co ...)
• Nice to go!

Answer 3

I know that this was after some time, but I found a solution using the hints given by SVN ... The update command is mainly used, as it states. Using CMD, I went to the workspace folder where the problematic project was located. Lets you call Project1. You call the command:

"svn upgrade project1"

this correctly resolved my problem without involving any hacking or workaround.

Answer 4

I had a similar problem, my svn is version 1.7.10, however my Subversion plugin for Eclipse is a bit older, I assume 1.6.something.

Using the rsync -arC working_directory archive_no_svn command was a breakthrough - at least now I had a copy of the synchronization clock that I just completed.

I tried using "svn co", but it was the wrong version, so I just started the update using the Subversion plugin in Eclipse - this restored the working directory from the repository - pretty much what I was after, and it was the correct version.

Getting rsync back to the right place was a trick. Rsync seems to remove the working folder to the archive location, creating archive_location / working_directory / the-files. Thus, synchronization of archived data back to working_directory was achieved with: rsync -ar archive_no_svn / working_directory.

Now I have to learn about updating my Subversion module for Eclipse to 1.7