Jump to content

TortoiseSVN 1.7 error


plumo
 Share

Recommended Posts

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 failed

NODES.presence may not be NULL

I 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 by plumo
Link to comment
Share on other sites

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).

Link to comment
Share on other sites

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 failed

NODES.presence may not be NULL

I 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 by stokescomp
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

  • 3 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...