On Mon, Oct 17, 2011 at 06:16:45PM +0200, Brockamp, Peter wrote: > So, as I see it now, this is in fact a *serious* problem at least with > TortoiseSVN > 1.7.0 working against an 1.6 SVN-server! So actually I must severly warn > about using > this configuration in a production environment, it will potentially cause you > problems!
No need to panic. First, this has nothing to do with client<->server interactions. It is a pure client-side problem. Second, there is no known case where a good 1.6 working copy failed to upgrade. Your errors are due to dormant problems in your 1.6 working copies, i.e. problems which you would have run into with 1.6 eventually. See http://subversion.tigris.org/issues/show_bug.cgi?id=4035 where Philip Martin reproduced your problem as follows: svn1.6 co file://`pwd`/repo wc -r1 svn1.6 rm wc/A svn1.6 add wc/A rm -rf wc/A svn upgrade wc This is clearly invalid operation, the directory wc/A should have been reverted with 'svn revert' rather than simply removed from disk. The upgrade should fail in this case, but apparently it doesn't. So there is something we can fix here, but it's not very serious. If you want to prevent your co-workers from running into this, just tell them to get fresh checkouts instead of upgrading. Especially if they have working copies which have been used for months or years.
