StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPointing SVN workspace to different server & repository with different parent directory
text
Body
copied!<p>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:</p> <pre><code>old repo: http://oldrepo/repositories/oldname/... new repo: http://newrepo/repositories/newname/... </code></pre> <p>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 <code>http://newrepo/repositories/newname</code>, the initial relocate seems successful. However, the workspace now believes the directory structure on the new repo looks like this:</p> <pre><code>http://newrepo/repositories/newname/oldname </code></pre> <p>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?</p> <p>Edit: The working directory is c:\SVN\FolderA. Performing the command: <code>svn relocate http://newrepo/repositories/newname/Folder1/FolderA</code> returns the following error:</p> <pre><code>svn: E155024: Invalid relocation destination: 'http://newrepo/repositories/newname/Folder1/FolderA' (does not point to target) </code></pre> <p>I am not sure how relevant this is, but the original repository location oldrepo was a folder, but in the new repository, newrepo (ie: <code>http://newrepo/repositories/newname</code>) 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.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload