[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[TSVN] Issues using TSVN on Solaris/samba drives

From: <Gavin.Kingsley_at_Powerware.com>
Date: 2005-08-11 00:19:48 CEST

Hello All,

I note that Sven has recently recommended using the CLI or a native client
for Unix working copies. We have recently switched from Sun Teamware to
SubVersion for source control with TSVN as our main client (running on
Windows, of course). We have noted the following issues:

(1) TSVN is very slow compared to using the CLI on Solaris.
(2) TSVN can incorrectly mark a file as changed. Not sure exactly why, but
it appears to be related somehow to the fact we are using a network drive
over samba and/or that we have svn:keywords=Id. Copying the directory with
the misreported file from Solaris copies the incorrect state for that file
but copying in Windows results in the file being marked as unchanged.
Comparing the Windows copy to the Solaris copy shows the files are the same
but some files were marked as executable in the Windows copy. Changing
those properties in the Solaris copy to match the Windows copy did not
correct the false report of an outstanding change in TSVN. If you commit
the file, the commit works without error and now you have two revisions of
the identical file.
(3) SVN revert on a replaced file does not appear to work well, but this
seems to be an SVN issue.

Are these issues why Sven made the recommendation not to use TSVN under
these circumstances? Are we attempting something that TSVN is not intended

By the way, I evaluated Rapid SVN and SubCommander as possible native
Solaris clients and I could crash them both easily. They seemed to be very
preliminary, especially compared to TSVN.

Gavin Kingsley.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Aug 11 00:20:22 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.