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

Re: Backup repository corrupted

From: Murli Varadachari <mvaradachari_at_facebook.com>
Date: Fri, 22 Feb 2008 10:30:11 -0800

That’s right — the rev# propertes do indicate 84332 as the last successful
sync.

Cheers
murli

On 2/22/08 10:05 AM, "Paul Koning" <Paul_Koning_at_Dell.com> wrote:

>>>>>> >>>>> "Murli" == Murli Varadachari <mvaradachari_at_facebook.com> writes:
>
> Murli> Thanks Paul — I was hoping there would be some other faster
> Murli> option but (sigh!) I guess in my case (3) is probably the best
> Murli> option.
>
> Murli> There may be another issue though — the rev# 0 properties on
> Murli> the restored backup would still indicate that last merged
> Murli> version as being 84333 [ even if I dumped and restored up to
> Murli> 84332 ]. Does this have to be fixed manually too?
>
> Probably. I don't have personal experience with svnsync; check the
> documentation on that feature.
>
> Then again, since the last svnsync failed, it probably didn't update
> the last sync'ed rev, which would mean the last successful one (84332)
> is correct. Take a look...
>
> paul
>
>
Received on 2008-02-22 19:55:11 CET

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.