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

Re: sqlite database errors through vm share

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Wed, 19 Dec 2012 21:14:18 +0100

On 19.12.2012 21:09, Oto BREZINA wrote:
> On 2012-12-19 18:53, Guido Leenders wrote:
>> I am having the same problem in our company (as discussed on this list 4 weeks ago). The problems have been halved approximately by making sure that both sides (Windows and Linux) run the same sqlite version. But it still sometimes occurs. The only really working workaround is to stick for all changes to one side.
> To be more clear.
> As I understand you use case, you do *ALL* svn operations in Win, while
> editing in Linux (no svn operations there).
> In this case you should have no locking problem except file permission
> mishmash may happen.
> If you share only versioned files but not version control between OSs,
> you should be safe. If you try to share control between OSs you are
> asking for trouble.
> So to move somewhere: do you any svn operations in Linux?

you should maybe read "How to corrupt your database files":

it seems to me that your VM doesn't have bug-free drivers or doesn't
implement the locking functions properly.

   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 2012-12-19 21:14:29 CET

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.