>Huh? Maybe I'm dense... your problem is about your wc somehow getting
>stuck and not receiving complete updates. The problem reported in this
>thread is totally unrelated. He's getting an out-of-date error during
>commits, and one that is expected.
>
Well, it's more probable that I am out in the blue :)
I'm not entirely sure of course, since I don't know exactly why all of our
wc's at work screwed up. But I suspect the problems are related since I
remembered now that what I had done before our problems occurred was just
that; added some files and moved some directories.
Is this was not the cause, our problems could possibly have had something to
with moving directories which contain non-versioned files in them. Something
along the lines of:
#Create repository and dir structure
svnadmin create /repos
svn mkdir file:///repos/trunk -m ""
svn mkdir file:///repos/trunk/test -m ""
svn mkdir file:///repos/trunk/test/to_be_moved -m ""
#User 1
svn checkout file:///repos/trunk trunk1
#User 2
svn checkout file:///repos/trunk trunk2
#User 1 moves the subdir
svn move trunk1/test/to_be_moved trunk1/test/moved
svn commit trunk1 -m ""
#User 2 obstructs the move by putting a file in the dir
cd trunk2
echo "" > test/to_be_moved/test.txt
#The update here fails correctly
svn update test
rm test/to_be_moved/test.txt
svn update test
Which fails with the error:
svn: Filesystem has no item
svn: file not found: transaction '7', path '/trunk/test/moved'
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 31 15:53:15 2003