TSVN Cleanup doesn't fix a locked WC while svn cleanup works (TSVN 1.9.7)

[Stefan Hett]

Hi,

this has been a long standing issue with the TSVN 1.9 client with one of
our external developers.

The developer is connected to the cooperate network via VPN. If he runs
an update using TSVN when the VPN connection is down (and he didn't
recognize before the update it was done) the result is that the WC is
locked.

When he tries to run TSVN clenaup, this doesn't resolve the locked
state. On the other hand, using the SVN command line client (svn
cleanup) unlocks the WC successfully.

This is apparently an issue ever since TSVN 1.9 (though I didn't track
it down reliably, so please understand this statement as a best guess).

Would you have any idea if there's any issue with the TSVN cleanup
implementation in this regard? I planned to take a look at that already
for several months, but unfortunately I never got enough spare time to
dig into it yet. Since the dev is complaining more frequently the past
weeks, I thought I give it at least a try and ask on the mailing list in
case this rings a bell.

Note: I still have it on my list to check out myself eventually (but
given I didn't get to it the past 6-12 months, I'm not sure if/when I'd
get to it).

--
Regards,
Stefan Hett, Developer/Administrator

[Stefan]

It depends on what checkboxes are set when doing the cleanup.
The svn library has problems with some combinations of the flags.

[Stefan Hett]

On 4/18/2018 4:47 PM, Stefan via TortoiseSVN wrote:

It depends on what checkboxes are set when doing the cleanup.
The svn library has problems with some combinations of the flags.

Thanks for the hint. Maybe this helps to trace the thing down if/once I get to check it out.

FTR: As far as I recall the dev explicitly tested to only have the "Clean up working copy status" setting in the dialog ticked:

I asked him to double check this next time. Unless I'm getting back on this, then this was actually the case.

[Stefan]

You have to check "Break write locks" as well. That's what removes the locks.

[Stefan Hett]

On 4/18/2018 7:52 PM, Stefan via TortoiseSVN wrote:
> You have to check "Break write locks" as well. That's what removes the
> locks.
>

Outch --- of course this was it --- I certainly mistook these for an
option to release the SVN locks (which is absolutely not what this
setting does). Thanks a lot for clearing this mystery.

Now it's only down to the fact to try to find a way to not leave the
lock there in the first place upon the SVN update call (but that's an
SVN thing and nothing for TSVN :) ).