SVN violations after moving
So, we recently moved our SVN server from the root path (svn: // sever /) to a subfolder (svn: // server / sub /) to allow multiple repos on the same server.
We already have a few working copies that we would like to just keep as is. Using Tortoise SVN, we ran the Relocate command and everything seemed to work great.
Except outside. All external items are relatively related (using the syntax ^/folder/ folder
), so the actual externals properties still work correctly ... The problem is that folders already checked against external properties still think they are related to the old path.
When I run the update, I get this error from all external ones:
'svn://server/old/folder/path'
is not the same repository as
'svn://server/sub'
Is there a way to fix working copies without having to manually delete / move all folders created with externals definitions? We have quite a few, and while this option works, I'm just wondering if there is a more automatic approach.
Thank!
source to share
svn st --ignore-externals
will display external values with status "X". You could build a script around this to find all external elements, then do svn switch --relocate ....
. If you only have external elements, you should be able to blindly navigate, but if you have such a point on another server, you need to add a step svn info
to ensure that the external one is the one that needs to be adjusted.
source to share