It seems this behavior has changed in 1.7 (to be released soon). It will no longer flag this as a tree conflict. See http://subversion.tigris.org/issues/show_bug.cgi?id=3526.
AFAICS, the case described here is similar to the one described in issue #3526. Patrick, if you have some time, maybe you can test this with one of the pre-releases of 1.7? See http://subversion.apache.org/packages.html#pre-release. Cheers, -- Johan On Wed, Jun 22, 2011 at 10:44 PM, Mark Phippard <markp...@gmail.com> wrote: > See http://subversion.apache.org/faq.html#self-tree-conflict > > > On Wed, Jun 22, 2011 at 4:04 PM, Patrick Quirk <p.qu...@smt.com> wrote: > >> ************** >> >> I’ve run into this issue the past few days and I don’t feel like this is >> expected behavior. I’m using client version 1.6.17 (Collabnet binaries). >> **** >> >> **** >> >> Simply put, I move a single file, commit that, then try to delete the >> directory the file was in (it’s empty now) and commit that. This fails, >> saying the directory I’m attempting to commit/delete is out of date. If I >> update it, I get a tree conflict. **** >> >> ** ** >> >> Am I wrong in expecting this to work without an update in the middle? >> I’ve provided a batch file to reproduce the behavior on a Windows machine >> (unzip and then change the file’s extension to .bat).**** >> >> **** >> >> Thanks**** >> >> Patrick**** >> >> ** ** >> >> ** ** >> >> ** ** >> >> **** >> >> **Patrick Quirk** >> GEM Software Engineer >> ****3511 University Drive**** >> ****Durham** **NC** **27707**** >> 919-354-4762 >> p.qu...@smt.com <p.qu...@sportsmedia.com> >> www.sportsmedia.com **** >> >> ** ** >> > > > > -- > Thanks > > Mark Phippard > http://markphip.blogspot.com/ >
<<image001.gif>>