Todd C. Gleason wrote:
> Hi all,
> I had described an error stealing locks using TortoiseSVN 1.5.8. I
> still have this problem with TSVN 1.6.1, but now I have an idea as to
> what triggers it. Here's as much information as I can give:
> First I identified a locked file using *Check for Modifications*, *Check
> Then I navigated to the file and used *TortoiseSVN->Get lock… *. I
> selected "Steal the locks". It doesn't seem to matter whether I use a
> message or not when trying to steal.
> I'm using https with NTLM authentication.
> In "servers" file:
> impac = *.impac.com
> http-library = serf
> Now, when I try this I get the error from the referenced message.
> If I comment out the line with "serf" and re-try, I can steal the lock.
> So, my guess is it's serf-related. It still only happens with TSVN, not
> with the command-line client from CollabNet, and I believe both respect
> the http-library setting, don't they?
when you type
$ svn --version
does it show
* ra_serf: Module for ...
If not, then serf is not compiled in your svn client and therefore won't
even use it, no matter what you've specified in your servers file.
TSVN uses the equivalent of
$ svn lock x:\path\to\file\to\lock --force
(don't forget the absolute path, not a relative one!).
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 2009-04-16 21:11:21 CEST