[ In general, this list prefers bottom-posting (i.e. putting your reply at the bottom) or inline replying. More below ... ]
On Sun, Aug 11, 2013 at 12:56 AM, <dlel...@rockwellcollins.com> wrote: > Hi Johan, > > I'll try and use the reproduction template, but will need to work this on > Monday as it appears I'll need to work the template a bit to work with > http://. I don't think the bug is related to the protocol. From what I've read so far, I think you should be able to reproduce this with file:// just as well (if not: that would be interesting additional information). Note that you can use "repository-relative externals" with ^/ etc, so you don't have to specify the protocol in your externals definition. > Here's the quick recipe.... > > Create a file external in svn:externals and commit it and perform full > update (foo.c rev 1). Please give the exact value you put into the property. There are a couple of variants of the syntax, and it's not clear whether you use a peg revision etc. > Create a new revision of the file and commit (foo.c rev 2) > Edit the svn:externals to point to latest revision (foo.c rev 2) And the exact syntax of the new value. > > Now here's the magic to reproduce the issue: > ;: > Only perform an "svn update . -depth empty --ignore-externals" // this > should bring in the new svn:externals property with foo.c rev 2 > Only update the file as "svn update foo.c" > > This should now show the file as being switched with an "svn status -v > foo.c": > > Performing a full "svn update" will cause the errors and seem to put the WC > into a bad state. -- Johan
