My working directory is on a drive on another PC on my LAN. This is because I
have just one licence for my compiler and it is tied to the hardware it was
installed on. There are two developers. Both of us check out our source code
to this third PC and compile there. The problem is that checking out to this
network share is slow and error prone.
We are using MS Windows (2000 pro) and subversion 1.0 with apache. The
subversion repository and apache are running on my PC (for the moment). When I
check out or update my source tree to my work area, the operation proceeds in
spurts and eventually stops indicating that a file already exists and it can't
be copied over. I can usually delete the offending file from my work area and
use the clean feature to remove locks. I can then restart the process. I
repeat these step a few times and eventually I have a complete set of sources to
I updated the network adapter (to 100 Mbit) in the PC where my working
directory is and this did improve the situation. Instead of cleaning and
restarting 10s of times, I only need to do it a few times.
I have installed subversion and tortoiseSVN on the machine containing the
network drive. A checkout operation initiated on this latter machine, to the
working area specified as a local dir (not using the network drive letter
mapping) completes successfully. The same operation where the working directory
is specified in terms of its network drive letter mapping, has problems.
Can't create a file when that file already exists."
To summarise: checking out to a working area specified in terms of a network
drive letter mapping is dodgy (for me here at least).
Is this a known bug? Any insights, work-arounds, comments etc would be greatly
Thanks and Cheers,
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Apr 19 04:20:36 2004