subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej <br...@wandisco.com>
Subject Re: wc.db: corruption after move?
Date Tue, 26 Nov 2013 17:27:53 GMT
On 26.11.2013 18:08, Philip Martin wrote:
> Marc Strapetz <marc.strapetz@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@wandisco.com

Mime
View raw message