Paul Charlton wrote:
> In the latest release TSVNCache has conflicted with
> both the cygwin SVN command line tool
1.) Out of curiosity, why would you use Cygwin for SVN when there are
native CLI utilities?
2.) TSVNCache shouldn't affect other SVN applications. When a file is
locked, the Subversion libraries that both the CLI utilities and TSVN
operate through simply waits a bit and retries. This is because,
other than TSVNCache, there are virus scanners, backup software and
such that will periodically lock files on Windows.
So in short, it should work.
You'll have to provide a bit more information than "it has conflicted"
if you expect anything deeper than the comments above :-).
Oh, and a hint. Stay clear of cygwin for mission-critical use, it has
severe bugs.
> and the TortoiseSVN utilties, leaving the .svn folders in
> a state where even the "cleanup" command does not work.
The Subversion working copy code lacks a lot in the 'safety' area,
unfortunately.
It's known that there are problems, but the incentive to do something
about it is not exactly high: people can work around the problem just
by checking out a new working copy, and there are more interesting/fun
things to work on.
That said, the correct thing to do when you have a completely wedged
working copy that 'cleanup' won't fix is to try and find your problem
in the Subversion issue tracker at
http://subversion.tigris.org/project_issues.html. If there's no
issue, report the problem on the Subversion mailing list, preferably
with a reproduction recipe.
> If this is not a known issue, I have three separate machines I can triage on
> to send you more information.
I've never seen or heard of it (the TSVNCache part).
More information would definitely be helpful :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Jan 17 13:13:25 2006