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
--
You received this message because you are subscribed to the Google Groups
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tortoisesvn/41064e2d-1bd2-c9e3-cb67-ca355dbf72b2%40egosoft.com.
For more options, visit https://groups.google.com/d/optout.
