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

Re: svn: E200030: sqlite: Expected database row missing

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 14 Oct 2014 13:03:02 +0100

Alexey Neyman <stilor_at_att.net> writes:

> On 10/13/2014 04:08 PM, Andreas Stieger wrote:
>> Hello,
>> On 09/10/14 23:48, Alexey Neyman wrote:
>>> What I was doing:
>>> - checked out a project from /trunk
>>> - did some local changes
>>> - copied WC to a branch
>>> - attempted to switch to the branch
>> What exactly does "copied WC to a branch" mean in terms of svn or file
>> system operations?
> It means exactly that, copying from a WC to a new directory in the repository:
> $ svn cp . ^/engr/aneyman/mybranch

That's a commit. Did it succeed? If so then the commit should contain
a lot of information about the state of the working copy. What does the
commit look like? What does 'svn log -v' show for the commit? Adds,
modifications, copies, deletes, property changes, etc.?
The tables in the SQLite database .svn/wc.db have some incorrect content
but it is hard to guess exactly what is wrong. The working copy is
complicated and you have provided little information. If there was no
corruption what sort of local changes do you expect? Adds, deletes,
property changes, etc.? Are there file or directory externals? Do they
have changes?

Are you able to identify which paths in the working copy trigger the
problem? Try running "svn st path", or "svn info path", for various
paths in the working copy, and see which succeed/fail.

Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2014-10-14 14:03:36 CEST

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.