(This is an email being sent to the support department at Syntevo, the
SmartSVN vendor, and is also being copied to the Subversion mailing list...)
We are running into a problem with SmartSVN, both the Foundation version
and the Professional version (with the 31-day evaluation license).
If someone has a file checked out and locked, SmartSVN will let me check
out the file and make my changes to it without warning me that the file is
locked. That's bad enough, but then when I go to check it back in SmartSVN
just hangs and give me the perpetual hourglass and gives me no way to
cancel the operation or even stop the program other than calling up Task
Manager and killing it.
If I then go in to the repository (as the user that locked the file) and
unlock it, SmartSVN still just stays in the "waiting" mode, won't detect
that the file has been unlocked. The only way I can get out of it is to go
into Windows Task Manager and kill the process.
This is a total show-stopper.
Now, I KNOW that one is not supposed to lock files when one checks them out
from Subversion, it defeats the whole concurrent versioning paradigm ...
but my co-developer on this project adamantly refuses to use Subversion at
all if he can't lock files, and also refuses to use it if it has to be used
from the command line ... and so unless we can get SmartSVN to handle
locked files in a logical manner (i.e. complain about the lock and refuse
to check in the file), he'll be back insisting that we use Visual Source
Safe with all of the liabilities that that entails.
(For the folks on the Subversion mailing list ... Yeah, I gave him all the
stuff that you guys gave me earlier today about VSS and how bad it is and
why. Didn't do any good.) :-(
I thought it might be an oddity of the Foundation version, so I got the
31-day evaluation license for the Professional version, and it's doing the
Subversion version is 1.3.2, and SmartSVN version is 2.0.7. Connection is
I rather badly need a fix for this ... any ideas?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Nov 8 06:05:57 2006