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

Re: Problem upgrading working copy

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Wed, 03 Aug 2011 20:55:07 +0200

On 03.08.2011 14:47, Markus Schaber wrote:
> Hi,
> I just upgraded to TSvn 1.7 beta2 for testing.
> With most working copies, this seemed to work fine (up to now), but with
> one specific one, I get the following error message:
> ---
> Subversion reported an error:
> database table is locked
> database table is locked: NODES

Did you run a cleanup with the 1.6 version first as recommended in the
release notes:
"To be on the safe side, you should run a cleanup with your pre-1.7 svn
client on your working copies. Because if the working copy is in an
inconsistent state, the upgrade process might fail. Best to run cleanup
before upgrading the svn client."



   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-08-03 20:55:31 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.