today I ran into an issue with TSVN. After a user-cancelled update, the
SVN directory was in a locked state. When trying to update a working
copy, I got the error message:
"Error: Working copy [foo] is locked.
Error: [foo] is already locked."
When trying to perform a clean-up, I get the following error:
"Cleanup failed to process the following paths:
Working copy [foo] locked.
[foo] is already locked."
Note that the initial error message (when trying to do an update) didn't
say that I should attempt a clean-up to solve the problem.
C:\Test\foo <- checkout of an SVN Repository
Steps to reproduce:
1. Update on C:\Test\foo\trunk
2. Cancel the update (by closing the update-dialog via the X-button)
3. Try to perform another update on C:\Test\foo\trunk
4. Try to perform an SVN cleanup on C:\Test\foo\trunk
It took me a while to realize the repo checkout was C:\Test\foo (not
C:\Test\foo\trunk) and I'd simply try to do an SVNCleanup on C:\Test\foo.
That actually did the trick and solved my problem.
Now I'm wondering whether it'd be a good idea to update TSVN's error
message in such a case to indicate that cleaning-up the
>>root<<-directory would be a possible way to solve the problem of the
Searching google for the error message I suspect that I'm not the only
one who ran into this situation. Normally users were given the
suggestion to do a clean checkout to solve this problem, which isn't
actually necessary in this case at all.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-03-20 09:40:41 CET