Re: wc-ng and recoverability of corrupt wc's

2011-07-01 Thread Philip Martin
Daniel Shahaf writes: > Philip Martin wrote on Fri, Jul 01, 2011 at 10:26:34 +0100: >> Corrupt pristine can be recovered by doing: >> >> $ svn up -r0 wc/some/path >> $ svn up wc >> >> That will also work for some, but by no means all, instances of corrupt >> metadata. >> > > And 'svn up --set-

Re: wc-ng and recoverability of corrupt wc's

2011-07-01 Thread Daniel Shahaf
Philip Martin wrote on Fri, Jul 01, 2011 at 10:26:34 +0100: > Johan Corveleyn writes: > > > AFAICS, this will no longer be possible with wc-ng. Has anyone thought > > about this problem? Any ideas on how one could recover "cheaply" from > > a small (local to a single directory or file) corruption

Re: wc-ng and recoverability of corrupt wc's

2011-07-01 Thread Johan Corveleyn
On Fri, Jul 1, 2011 at 11:32 AM, Noorul Islam K M wrote: > Johan Corveleyn writes: > >> Hi, >> >> Sometimes, a (part of a) working copy gets corrupted (errors like >> 'checksum mismatch ...' while running 'update'). Maybe it happened >> because a third-party tool has messed with the base files, o

Re: wc-ng and recoverability of corrupt wc's

2011-07-01 Thread Noorul Islam K M
Johan Corveleyn writes: > Hi, > > Sometimes, a (part of a) working copy gets corrupted (errors like > 'checksum mismatch ...' while running 'update'). Maybe it happened > because a third-party tool has messed with the base files, or with the > entries file, or ... or maybe it happened because of

Re: wc-ng and recoverability of corrupt wc's

2011-07-01 Thread Philip Martin
Johan Corveleyn writes: > AFAICS, this will no longer be possible with wc-ng. Has anyone thought > about this problem? Any ideas on how one could recover "cheaply" from > a small (local to a single directory or file) corruption in the wc > (either incorrect meta-data, or corrupt pristine, or ...)

wc-ng and recoverability of corrupt wc's

2011-07-01 Thread Johan Corveleyn
Hi, Sometimes, a (part of a) working copy gets corrupted (errors like 'checksum mismatch ...' while running 'update'). Maybe it happened because a third-party tool has messed with the base files, or with the entries file, or ... or maybe it happened because of a bug in svn. This was/is deemed non-