I can appreciate the need for more complete info -- I will follow up with
more specific evidence. What I can say for sure is that three separate
machines which were working fine with SVN 1.26 suddenly all exhibited the
same undesirable behavior soon after upgrading to 1.30 5416. All systems
affected are 32-bit Win32 XP SP2.
1) cygwin svn is used basically as a readonly client for an automated cross
platform build system --- the use of generic build scripts for *NIX and
Win32 has been a benefit -- and is not truly mission critical.
2) the problems went away completely when TSVNCache.exe [rev 1.30 5416] was
renamed so that it could not be autostarted --
I will put in a plug for getting functionality similar to Perforce
"Integrate" with its documentation features, and for separate tools for
visualizing and managing codelines --- I'd even consider volunteering to
work on those sort of tools for SVN.
----- Original Message -----
From: "Molle Bestefich" <molle.bestefich@gmail.com>
To: <dev@tortoisesvn.tigris.org>
Cc: <mystic@netcabletv.net>
Sent: Tuesday, January 17, 2006 4:12 AM
Subject: Re: Tortoise 1.30 5416
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 23:48:55 2006