Strange SVN behavior (missing files) when using depth immediates followed by depth infinity -
alright, have strange 1 pick brains about.
- repository:
- revision 0: empty
- revision 1:
dir1/f1.txt
- revision 2:
dir1/f1.txt
,dir1/f2.txt
,dir2/f3.txt
your typical, right?
now strangeness. svn 1.6.5 , 1.6.13 alike. i'm not going able upgrade try rid of this. i'm running these commands in working copy root.
- commands
svn update -r1
- update revision 1 successful, working copy looks good.svn update --depth immediates
- good,dir2
gets created , empty, no other changes.svn update dir1 --set-depth infinity
- svn says ok,dir1/f2.txt
won't pop in working copy.svn update
- cause i'm getting anxious - nothing,dir1/f2.txt
still wont pop up.svn update -r1
- error:dir1/f2.txt
not under version control (whoa?)svn update
-dir1/f2.txt
in.
if knows why dir1/f2.txt
refuses appear when run step 3 , what, if anything, doing wrong, please share.
this has been confirmed bug in svn 1.6. resolution upgrade svn 1.7 or svn 1.8.
from horse's mouth (the svn dev list):
on thu, aug 8, 2013 @ 1:34 pm, philip martin wrote:
svnadmin create repo svnmucc -mm -u file://`pwd`/repo mkdir d1 put repo/format d1/f1 svnmucc -mm -u file://`pwd`/repo put d1/f2 mkdir d2 put repo/format d2/f3 svn co file://`pwd`/repo@1 wc svn --depth immediates wc svn --set-depth infinity wc/d1 svn st -v wc
with 1.7 , 1.8 status shows
2 2 pm wc 2 2 pm wc/d1 2 1 pm wc/d1/f1 2 2 pm wc/d1/f2 2 2 pm wc/d2
with 1.6 status shows
2 2 pm wc 2 2 pm wc/d2 2 2 pm wc/d1 2 1 pm wc/d1/f1
so bug in 1.6 fixed in 1.7 , 1.8.
-- philip martin | subversion committer wandisco | non-stop data
Comments
Post a Comment