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

Re: wc.db: corruption after move?

From: Branko Čibej <brane_at_wandisco.com>
Date: Tue, 26 Nov 2013 18:27:53 +0100

On 26.11.2013 18:08, Philip Martin wrote:
> Marc Strapetz <marc.strapetz_at_syntevo.com> writes:
>> We are encountering working copies with
>> nodes.presence = moved and nodes.moved_to = <null>
> What does "nodes.presence = moved" mean? There has never been a moved
> presence.
> Do you mean rows with nodes.moved_here=1 no corresponding rows with
> non-null nodes.moved_to? Or something else?
>> As far as I have been told, this has already been fixed and backported
>> to 1.8.5. Still, for those users which already have this corruption, is
>> there a way to recover their working copies with standard Subversion
>> functionality? Could a Revert work? And if it currently does not, could
>> the Revert be more tolerant, so it could handle such cases?
> What operation is failing? Are you getting some error?

Marc is looking at some code that converts wc.db info to some internal
structure ...

Marc, can you please explain how the wc.db itself looks like? Hint: we
don't support SmartSVN or SVNKit here. :)

-- Brane

Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane_at_wandisco.com
Received on 2013-11-26 18:28:31 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.