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

RE: Problems with exclusive-locking

From: bugreport <M8R-fj4tn21_at_thisisnotmyrealemail.com>
Date: Thu, 27 Feb 2014 03:14:45 -0800 (PST)

Another point to add: As the update dialogue still have a lock all "resolve conflict" commands wait for the lock.
But: There is no information about that. The following just happened:
- did TSVN->update
- got a conflict
- tried to resolve the conflict via double click, nothing happened
- double clicked again 2 times, nothing happened
- switched to an open TSVN->commit dialoge and using double click and context menu -> resolve conflict there, nothing happened
- ended the TSVN->update dialogue, the last (not timed out?) 3 "resolve conflict" actions are done (the conflict editor was opened three times)

Can we issue a message here, too? The command line tools output a sqlite[S5] message in this case.

... and after some testing:
all svn actions are blocked as long as the TSVN->update dialoge is open, even if it displays a sqlite[S5] error on its own, as soon as it is closed all svn actions work again (despite of (t)svn->commit which worked after TSVN->cleanup)


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-02-27 12:14:52 CET

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