I have 2 questions that are somewhat related. The first one is a usability
issue with TortoiseSVN update command, and the other is with performing
updates to selectively built local directory trees.
Let me start by setting up a scenario. Assume that we have a repository
with the following structure
Now, locally, I would like an svn controlled directory structure with some,
but not ALL of the above directories, to look like this:
Notice that I don't want area2, and area4 checked out local.
So here, source, area1 and area3 all have a .svn directory, and the entries
file of source lists only area1 and area3. Originally, I thought the way to
do this was to (using TortoiseSVN) do a checkout (do not recurse) of
source, then a checkout of area1 and area3 into source. I found that this
creates 3 independent local svn controlled directories ie. the entries file
of source would not list area1 and area3. So, if I did and update on the
source directory, it wouldn't recursively update the area1 and area3
I discovered that I could start by doing a checkout (non-recursive) of
source, and then using the COMMAND LINE svn, do and 'svn update area1
area3' in the source directory. This would grab the required
subdirectories, update the source/.svn/entries file accordingly. I'd end up
with a fully locally built and controlled set of directories. I could now
do an update on the source directory, and it would recursively update area1
So, the first problem is here-I cannot use TortoiseSVN to do the svn update
command for a single directory that does not locally exist. If I
right-click source, and do the SVN Update listed, there are no further
options. It just does a default svn update with no specified parameters.
The second problem I have is, after setting up my directory as above, I
would go to do a top level update (update on source) and get a message
Working copy s:/source/area2 is missing or not locked
Please execute the "Cleanup" command.
1. I did not WANT area2
2. I notice that source/.svn/entries has obtained an attribute incomplete
="true" in the entry tag
3. On a subsequent update, it goes ahead and grabs the area2, and area4
directories out local-I don't want these!
I've found a work around. If after the message is displayed I edit the
entries file and remove the incomplete="true" attribute, I can then again
do an update and it seems to work fine. This is OK for me, but trying to
show all the developers how to get around this problem is a pain.
1. Is it possible (or can it be added) to get TortoiseSVN to specify
--non-recursive, selective directories, and other parameters for the update
2. Is this 'missing or not locked' message a bug? -maybe I'm approaching
this problem (for selective local directories) the wrong way.
Any help here would be greatly appreciated!
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Apr 12 13:38:26 2005