> > Also, the Subversion 1.5.5 client, with option "-force", seems to
> > this fine and steals the lock as requested. Another workaround is
> > use the repo-browser to break the lock first.
> > Is it possible that the "steal the locks" checkbox is being ignored?
> I've tried this with the latest nightly build, and it works as
> And I don't see anything in my 1.5.x files that would suggest that the
> checkbox is ignored.
> Could you maybe try a nightly build?
I tried with
And it still doesn't work. The error message looks just a little
Lock failed: [local path]
Error: '[repo path]'
Error: is already locked by user '[other user]' in filesystem '[repo
Some other things I note: If I lock using the command line (which I
have to do in a separate WC since I have 1.5.5 cmd line) and then try to
update in this WC, TSVN doesn't "see" the lock I now have. It used to
handle this just fine, I thought. And if I try to commit when my other
WC has a lock, it still fails, telling me that user (me!) has the file
So to commit a file I stole the lock, then released it, then quickly
committed. (I could have broken the lock and committed too, of course.)
Yet you say it works with the latest nightly build. Is there some
possible server configuration involved here, or a possible problem
related to using a 1.5.2 server?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-03-06 20:43:18 CET