Well that is the problem. The last backup was a few days old so the
working copies are later.
So I tried to just relocate to the exact same directory (just to see if
it worked) and though it said it relocated... when I tried to update it
said "Revision x does not exist". Would this message go away if I
actually moved the location? I am a little confused on the location. Do
I just switch it in my Apache conf (Location /projects)?
<Location /projects>
DAV svn
SVNPath C:\svn\myrepos
AuthType Basic
AuthName "Subversion Repositories"
AuthUserFile passwd
AuthzSVNAccessFile svnaccessfile
Require valid-user
</Location>
What is the normal restore procedure in this case? It would be nice to
just be able to update and the working copy "gets its bearings".
Thanks for the reply.
-----Original Message-----
From: Erik Huelsmann [mailto:ehuels@gmail.com]
Sent: Friday, November 25, 2005 7:10 AM
To: Bryan D. Andrews
Cc: users@subversion.tigris.org
Subject: Re: RE: RE: svnadmin dump - Help Appreciated
On 11/25/05, Bryan D. Andrews <bandrews@trendcore.com> wrote:
> We actually just had to restore our repos again (harddrive issue) and
I
> was wondering if there were any alternatives to our devs all having to
> check out fresh working copies from source and copying their code back
> over it?
If you reloaded all dumps, so that no working copy is past the last
revision, then you should be able to keep using your repository with
the existing working copies.
Also, if you restored it at a different location, you may be able to
let your users switch to it using 'svn switch --relocate'.
HTH,
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 25 16:39:49 2005