[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: E235000: assertion failed (SVN_IS_VALID_REVNUM(new_revision))

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Wed, 21 Jan 2015 12:05:59 +0000

Tomasz Grobelny <tomasz.grobelny_at_makingwaves.pl> writes:

> I am trying to commit a change to a repository on codeplex, but I am unable to do so:
>
> D:\Projects\openwaves\OpenWaves.EPiServer\trunk\src>"C:\Program Files\TortoiseSVN\bin\svn.exe" commit -m " - add OpenWaves.EPiServer6 on trunk branch"
> Sending OpenWaves.EPiServer.sln
> Adding OpenWaves.EPiServer6
> Sending OpenWaves.EPiServer6\EPiVirtualPathFileProvider.cs
> Deleting OpenWaves.EPiServer6\OpenWaves.EPiServer.csproj
> Deleting OpenWaves.EPiServer6\OpenWaves.EPiServer.nuspec
> Adding OpenWaves.EPiServer6\OpenWaves.EPiServer6.csproj
> Adding OpenWaves.EPiServer6\OpenWaves.EPiServer6.nuspec
> Sending OpenWaves.EPiServer6\packages.config
> Transmitting file data ....svn: E235000: In file 'D:\Development\SVN\Releases\TortoiseSVN-1.8.10\ext\subversion\subversion\libsvn_wc\wc_db.c' line 11342: assert
> ion failed (SVN_IS_VALID_REVNUM(new_revision))
>
> Any ideas how can I start debugging the issue?

That's failed in the code that runs on the client after the commit has
succeeded. It appears that the the client is acting as if the commit
worked on the server but it has not got the newly committed revision.
If you look at the server/repository did the commit succeed?

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2015-01-21 13:07:14 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.