You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by richard hornsby <ri...@gmail.com> on 2008/01/08 18:43:40 UTC

svn_wc__entry_modify: Assertion failed

Hi guys,

Having a strange issue with the svn client crashing (core dump) on me.
 Problem was in 1.4.3 (ubuntu packages), so I upgraded (compiled)
1.4.6 and it still crashes with the message (transcription below)

svn: subversion/libsvn_wc/entries.c:2444: svn_wc__entry_modify: Assertion
`orig_schedule == entry->schedule' failed.
Aborted (core dumped)

We're using extjs (a relatively large set of files) and keep a copy of
it in our svn repo with the rest of our
"common" code.  When I went to upgrade from 1.x to 2.0, the only way I
could think to _replace_ it was to svn rm the whole directory, and
then re-add the new version.  Adding the directory, however, causes
svn to crash:

$ svn --version
svn, version 1.4.6 (r28521)

$ svn add extjs
svn: subversion/libsvn_wc/entries.c:2444: svn_wc__entry_modify: Assertion
`orig_schedule == entry->schedule' failed.
Aborted (core dumped)
$ svn stat
?      extjs-1.1.1
?      extjs
?      ext-2.0.zip
  L    .

If I try something else, it seems to work okay:

$ svn cleanup
$ mkdir test
$ svn add test
A         test

$ find extjs -name '.svn'
[no output]

I'm not sure where the core file is ending up, and it might not be
getting written to disk based on a system config value (IIRC).  Please
let me know what info I can provide without being too verbose.


thanks guys

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org