Re: Cleanup needed after failed update
From: Justin Case <send_lotsa_spam_here_at_yahoo.com>
Date: Tue, 12 Jun 2012 04:52:01 -0700 (PDT)
> From: Johan Corveleyn <jcorvel_at_gmail.com>
Thank you for the explanation. I was also expecting what Andreas said - the update command should be able to manage its own locks. It's not like it met some unknown SVN locks, but the file was simply in use. I also see this behavior coming only recently since I upgraded to TortoiseSVN 1.7.something - I cannot tell you which commands the client sends, or which version of svn it was previously using, just that the Tortoise guys said it's not their ball.
Here's my very simple test case:
In any case, I certainly hope the new version doesn't expect from me, the user, telling it whether the lock is a stale one or if there's some other command hanging on it...
This is an archived mail posted to the Subversion Users mailing list.