RE: E235000: assertion failed (SVN_IS_VALID_REVNUM(new_revision))
From: Tomasz Grobelny <tomasz.grobelny_at_makingwaves.pl>
Date: Wed, 21 Jan 2015 16:47:09 +0000
I am afraid that this may no longer be possible as I took a workaround and committed my changes using TFS interface to codeplex repo.
Not sure if it helps tracking down the issue, but this is all I can remember to reproduce the issue right now.
Tomek
-----Original Message-----
Tomasz Grobelny <tomasz.grobelny_at_makingwaves.pl> writes:
>> That's failed in the code that runs on the client after the commit
The client sends an HTTP MERGE request to make a commit. When the commit is successful the server sends a 200 OK response that includes the new revision number and the client updates the working copy. In your case it seems the server sent a response that the client interpreted as a successful commit but without the new revision number.
The client may have broken the working copy when it tried to apply the missing revision number. You may have to check out a second working copy, compare to the first and manually transfer the changes to the second working copy.
-- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*Received on 2015-01-21 17:48:47 CET |
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.