plumo Posted October 14, 2011 Report Share Posted October 14, 2011 (edited) I updated tortoiseSVN to version 1.7 . Then I needed to click "SVN upgrade working copy" on 0 A.D. to change to the new 1.7 format.While TortoiseSVN was processing the files I got the error: Subversion reported an error:constraint failedNODES.presence may not be NULLI know I can always downgrade to version 16.xx but I wanted to report his anyhow. Who knows if this error is related to Tortoise itself or 0 AD.Cheers. Edited October 14, 2011 by plumo Quote Link to comment Share on other sites More sharing options...
janwas Posted October 14, 2011 Report Share Posted October 14, 2011 Thanks for the report, this will serve as a warning to anyone wanting to upgrade A search for that error message didn't turn up anything. Might want to report it to the SVN mailing list.In the meantime, it's probably best to check out a fresh working copy with 1.7 (or downgrade as you've mentioned). Quote Link to comment Share on other sites More sharing options...
stokescomp Posted October 18, 2011 Report Share Posted October 18, 2011 (edited) I updated tortoiseSVN to version 1.7 . Then I needed to click "SVN upgrade working copy" on 0 A.D. to change to the new 1.7 format.While TortoiseSVN was processing the files I got the error: Subversion reported an error:constraint failedNODES.presence may not be NULLI know I can always downgrade to version 16.xx but I wanted to report his anyhow. Who knows if this error is related to Tortoise itself or 0 AD.Cheers.I think its something in the binaries folder that causes this. It stopped at the binaries/log folder everytime when it gets this error so I just deleted the binaries folder and then upgraded and it worked. Now I just have to update the binaries folder.update: I have fixed it by just deleting this folder: AD0_RTS\binaries\system and then updating that folder. The rest of the binaries folder was not the problem. The system folder is only 200MB or so. so that's not too bad.I am using the public url Edited October 18, 2011 by stokescomp Quote Link to comment Share on other sites More sharing options...
Ykkrosh Posted October 18, 2011 Report Share Posted October 18, 2011 I just upgraded from TortoiseSVN 1.6.12 to 1.7.0 (on 64-bit Win7) and upgraded the working copy, and it seems to have worked with no problems. This is with the non-public SVN URL, not the public read-only one; I'm not sure if that would cause a difference. Quote Link to comment Share on other sites More sharing options...
historic_bruno Posted October 18, 2011 Report Share Posted October 18, 2011 I got this problem with public SVN on OS X after upgrading to SVN 1.7. Which is annoying because it was a fresh install of Lion and MacPorts installed 1.7 by default, so I had to manually get an older revision of the port and downgrade to avoid downloading GBs again Quote Link to comment Share on other sites More sharing options...
Ykkrosh Posted October 19, 2011 Report Share Posted October 19, 2011 stokescomp on IRC pointed to this bug causing errors like "Failed to mark '...\docs\internal' absent: item of the same name is already scheduled for addition" when upgrading. Might be best to wait for 1.7.1 which ought to fix that bug. Quote Link to comment Share on other sites More sharing options...
plumo Posted November 9, 2011 Author Report Share Posted November 9, 2011 Now that 1.7.1. is released, has it been fixed ? Can't find it in the release notes. Quote Link to comment Share on other sites More sharing options...
historic_bruno Posted November 12, 2011 Report Share Posted November 12, 2011 Now that 1.7.1. is released, has it been fixed ? Can't find it in the release notes.Looks like it, I just upgraded a public checkout on OS X from SVN 1.6 to 1.7.1 with no errors Quote Link to comment Share on other sites More sharing options...
plumo Posted November 14, 2011 Author Report Share Posted November 14, 2011 Same for me ! Topic can be locked . Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.