On Thu, Sep 3, 2009 at 8:12 AM, Mac Newbold <mac_at_codegreene.com> wrote:
> In older versions of subversion, it seems that the --relocate switch would
> let you change the URL to your repository without needing to contact the
> old repository nor the new one. It would simply make the changes to the
> local working copy.
> In current documentation here:
> It looks like that has changed, and now it insists on accessing the URL
> before it will carry out the changes to the working copy.
> Is there any way to get the old behavior again? I tried the --force
> switch, but it still fails if it can't contact the new repo.
> My situation is this: I need to run a switch --relocate under conditions
> where I can't connect to the new repo, but still need to make the changes
> to the working copy so that I can access the repo properly later.
> Any ideas?
> I'm all in favor of sanity checking, as long as there's a way to override
> it with a flag for "i know what I'm doing", which I thought is what
> --force was intended to be. Maybe a "don't access the network" flag would
> be even better.
> If svn itself refuses to do it, I guess I'm back to using perl or sed to
> do the replacement in the .svn/entries files...
Just out of curiosity, why not just wait until you have network access to
the new repository before running 'svn switch'?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-03 01:57:30 CEST