RE: RE: RE: svnadmin dump - Help Appreciated

["Bryan D. Andrews" <ba...@trendcore.com>]

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?

Thanks for any info.

TortoiseSVN 1.2.4, Build 4479 - 32 Bit
Subversion 1.2.3, 
apr 0.9.6
apr-iconv 0.9.5
apr-utils 0.9.6
berkeley db 4.3.28
neon 0.24.7
OpenSSL 0.9.8 05 Jul 2005
zlib 1.2.3


-----Original Message-----
From: Bryan D. Andrews [mailto:bandrews@trendcore.com] 
Sent: Friday, July 29, 2005 3:19 PM
To: users@subversion.tigris.org
Subject: RE: RE: svnadmin dump - Help Appreciated

Well by the silence (and the lack of hits on google) I am guessing this
is not good. I tried recover and a few other things to no avail.

I have loaded my last dump and was trying to figure out how I should
handle this on the client side. A simple update does not work as
expected... reporting that the last revision does not exist.

Do I have to export every working copy and check out, and paste over the
new working copy to get this back going again? I hope there is an easier
way I am missing.

Thanks for any suggestions.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: RE: RE: svnadmin dump - Help Appreciated

[Erik Huelsmann <eh...@gmail.com>]

On 11/25/05, Bryan D. Andrews <ba...@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.