Question

I have an svn repository that is slated EOL, and the various projects are being moved through svnrdump dump and svnadmin load to a new repository. For the purposes of discussion, the basic topology is:

old repo:  http://oldrepo/repositories/oldname/...
new repo:  http://newrepo/repositories/newname/...

This particular repository is large and I have a developer wishing to point his old workspace to the new repository. The problem that I am seeing is that TortoiseSVN allow a relocate event, and by entering the URL http://newrepo/repositories/newname, the initial relocate seems successful. However, the workspace now believes the directory structure on the new repo looks like this:

http://newrepo/repositories/newname/oldname

Is there a way to remove the workspace’s reference to oldname? Because of the extra unintended directory, an SVN update fails. The only option I can think of is to have this developer checkout the entire needed workspace fresh from the new repository, and have him copy his WIP files into the new workspace. Are there other options or solutions on the client side?

Edit: The working directory is c:\SVN\FolderA. Performing the command: svn relocate http://newrepo/repositories/newname/Folder1/FolderA returns the following error:

svn: E155024: Invalid relocation destination: 'http://newrepo/repositories/newname/Folder1/FolderA' (does not point to target)

I am not sure how relevant this is, but the original repository location oldrepo was a folder, but in the new repository, newrepo (ie: http://newrepo/repositories/newname) is the root level for the new repository. Also, I should point out that during the migration, the changes were preserved but the individual version numbers were not.

Answer 1

Your developer will probably have to:

• Disconnect his project from the old workspace
• Save his uncommitted changes (if any) somewhere else
• Delete his project
• Export his project from the new workspace
• Reapply his uncommitted changes (if any) to the project