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

Re: libsvn_ra_svn\marshal.c line 486: assertion failed (opt || cstr)

From: Stein Somers <ssomers_at_opnet.com>
Date: Tue, 15 Sep 2009 20:33:51 +0200

Stefan Sperling wrote:
> subversion/svn/update-cmd.c:96: (apr_err=210000)
> subversion/libsvn_client/update.c:371: (apr_err=210000)
> subversion/libsvn_client/update.c:294: (apr_err=210000)
> subversion/libsvn_wc/deprecated.c:149: (apr_err=210000)
> subversion/libsvn_ra_svn/client.c:296: (apr_err=210000)
> subversion/svnserve/serve.c:851: (apr_err=210000)
> svn: Special code for wrapping server errors to report to client
> subversion/libsvn_wc/update_editor.c:2001: (apr_err=150000)
> subversion/libsvn_wc/entries.c:1325: (apr_err=150000)
> svn: 'bug2/trunk2/alpha' is not under version control

One thing that puzzles me: svn sends all this gibberish your way, but you say
you can't reproduce the problem? Seems to me you don't see the devil in the
shape I do, but you do see the problem that the state of the working copy
causes the last svn update to bark at you.

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-15 20:34:36 CEST

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.