Hi, I've been using SVNKit to programmatically do some commits for a while now (great library!).
I'd previously been using v.1.7.8 against a SVN v1.6.16 server (part of a Trac 0.12 installation) with no problems. I also used TortoiseSVN v1.7 (on Windows) to manage the working copy. I recently upgraded to TortoiseSVN v1.8.7 and, because that's using the 1.8 working copy format, upgraded SVNKit to v1.8.5. Now (*perhaps* coincidentally) all my SVNKit commits are failing with E204899 errors talking about being unable to rename internal SVN files in .svn\tmp directories similar to the below: Cannot rename file 'RootDir\.svn\tmp\file.xml.tmp' to 'RootDir\DirA\DirB\file.xml' (Where the rename target is an SVN-controlled file that has changed for this commit.) My understanding is that SVNKit 1.8 should work fine with a 1.6 server. Is TortoiseSVN possibly interfering in some way? If it's relevant, the file it is trying to rename to is one I programmatically write to just before the commit; i.e., it's an SVN-controlled file which I overwrite using standard Java I/O operations. None of my code has changed from when it worked. Any ideas would be much appreciated. Stuart
