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

Re: line 1801: assertion failed (SVN_IS_VALID_REVNUM(changed_rev)) [SEC=UNCLASSIFIED]

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Wed, 29 Jan 2014 11:21:37 +0000

"Levy, Gabriel (Contractor)" <Gabriel.Levy_at_dsto.defence.gov.au> writes:

> I've upgraded from TortoiseSVN 1.7.3 (build 22386) using Subversion
> 1.7.2 to TortoiseSVN 1.8.4 which uses Subversion 1.8.5 Now I'm getting
> almost every time I try to checkout a project tree with externals in
> it, the following Exception/Assertion at random times:

> In file
> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.4\ext\subversion\subversion\libsvn_wc\wc_db.c'
> line 1801: assertion failed (SVN_IS_VALID_REVNUM(changed_rev))

That's the changed_rev parameter passed to svn_wc__db_base_add_file,
which is only called from update_editor.c:close_file. The changed_rev
value should have been extracted from the entry property in

What do your svn:externals look like, what format do they use? Are they
within the same repository or to different repositories? Are they file
or directory externals? I don't think file externals cause a call to
svn_wc__db_base_add_file so it's either a directory external or the main
working copy that is triggering the error.

Which server version are you using? Which protocol? Which
server/protocol for the externals?

Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2014-01-29 12:22:17 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.