[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

SVN update of child ignores files if preceded by update --depth immediates

From: Mihai Danila <viridium_at_gmail.com>
Date: Wed, 7 Aug 2013 23:18:35 -0400

With Subversion 1.6.5, 1.6.13, and I believe Subversion 1.7 also, I noticed
the following bug, which I first asked about on StackOverflow about and had
independently confirmed (
http://stackoverflow.com/questions/18114102/strange-svn-behavior-missing-files-when-using-depth-immediates-followed-by-dep
).

I will copy straight from there.

   - Repository:
      - Revision 0: empty
      - Revision 1: dir1/f1.txt
      - Revision 2: dir1/f1.txt, dir1/f2.txt, dir2/f3.txt

Your typical, right?
------------------------------

Now for the strangeness. I'm running these commands in the WC root.

   - Commands
      1. svn update -r1 - Update to revision 1 is successful, working copy
      looks good.
      2. svn update --depth immediates - All good, dir2 gets created and is
      empty, no other changes.
      3. svn update dir1 --set-depth infinity - SVN says OK, but
dir1/f2.txt just
      won't pop up in my working copy.
      4. svn update - just cause I'm getting anxious - nothing,
dir1/f2.txt still
      wont pop up.
      5. svn update -r1 - Error: dir1/f2.txt is not under version control
      (WHOA?)
      6. svn update - Now I get dir1/f2.txt in.
Received on 2013-08-08 18:28:09 CEST

This is an archived mail posted to the Subversion Dev mailing list.