[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Reorganized repository, cannot update

From: John Szakmeister <john_at_szakmeister.net>
Date: 2003-12-15 10:59:17 CET

On Monday 15 December 2003 04:19, Tristan Seligmann wrote:
> > Yep, that's pretty much it. The directory it's trying to update to
> > disappeared, so now it's a little confused. No worries though, use the
> > 'svn switch --relocate' command to move it to your new URL. This will
> > update you WC with the new URL, and you'll be ready to go.
>
> This doesn't seem to help; running update on the relocated working copy
> gives me the same error. (I'm using the TSVN relocate command, which is
> presumably the same as svn switch --relocate).

You're right, running 'svn up' after the switch still fails with the same
error. The reason is because svn_repos_dir_delta() is trying to find /
qmaster/trunk in the repository at rev X (a revision before committing the
changes to move /trunk/qmaster to its new location), and well, it doesn't
exist there.

So, I guess there are a couple of answers here to prevent losing your local
modifications. You can go ahead and try to commit your changes (if they're
ready to be committed). As long as someone hasn't done anything to cause a
conflict, this should work without a problem. Or, you can run 'svn diff > /
path/to/somewhere/safe/local-mods.patch' to save off your current changes,
remove the working copy, checkout a new one, and apply the patch with the
'patch' tool. You working copy will now have your local mods inserted back
in.

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 15 10:54:56 2003

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.