[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: Robin Guest <robin.guest_at_gmail.com>
Date: Thu, 4 Aug 2011 08:34:06 +0100

On 4 August 2011 08:26, Markus Schaber <m.schaber_at_3s-software.com> wrote:
> Hi, Stefan,
> Von: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
>> > 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."
>> http://tortoisesvn.net/tsvn_1.7_releasenotes.html
> I did so, but only after the first failed upgrade. However, the .svn directory in the working copy looks rather untouched (no pristine directory and no wc.db file), and the svn cleanup finishes without any output.

That's cleanup from a *pre*-1.7 client. Have you tried svn cleanup
from a 1.6 command line client?

> Btw, is it possible to keep TortoiseSVN 1.6 in parallel to 1.7, for purposes of migration ease?

See above. You can keep your command line client at 1.6 while you are
upgrading your working copies.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-08-04 09:34:13 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.