subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Sperling <s...@elego.de>
Subject Re: svn cleanup fails to clean up
Date Tue, 08 May 2012 10:08:32 GMT
On Tue, May 08, 2012 at 10:54:01AM +0200, Niemann, Hartmut wrote:
> svn: E155016: Missing a row in WCROOT.

The working copy meta data is corrupt. It's not easy to fix.

It is possible that just this one row got corrupted, and that it could
be fixed with some sql commands. But even then I would not trust this
working copy anymore. You should get a fresh checkout.

> Is there a force mode in svn cleanup?

No.

> In my opinion svn cleanup should never fail without giving advice what to try next.

That would be great but it is not very easy to do.
What do you expect the software to do? Figuring out what sql statements
to run to fix broken database tables is hard to do in software.
Subversion has no artificial intelligence built-in, unfortunately ;)

> Could svn cleanup correct this SQL table problem?

No. 'svn cleanup' removes stale lock files that usually prevent concurrent
modifications of working copy meta-data by separate client instances.
It must be used when an svn client crashes midway or is in some other
way prevented from cleanly finishing up an operation. 'svn cleanup' has
no knowledge of the sql tables used in working copy meta data.

> Is this a bug to be reported in the bugtracker? (Where?)

If you can present a series of steps that will reliably trigger a
problem such as this, an entry in the tracker is warranted.

However, if there is a possibility that the antivirus software damaged
or otherwise interfered with the sqlite database file that is not a bug
in Subversion.

Mime
View raw message