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

Re: anyone else seen this assertion error?

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-06-02 00:49:09 CEST

Rick Jones <rick.jones2@hp.com> writes:
> Transmitting file data ......svn:
> /build/buildd/subversion-1.4.2dfsg1/subversion/libsvn_client/commit.c:1596:
> svn_client_commit3: Assertion `*commit_info_p' failed.
> Aborted
> raj@tardy:~/netperf2_trunk$

No. Is it reliably reproducible? (And if so, with latest trunk build?)

> and then after a while an svn status starts to claim certain files are
> locked when I've not done anything of the sort:

This "L"s don't refer to the repository-path locking feature, they are
working copy administrative locks. 'svn cleanup' should take care of
them.

-Karl

-- 
Subversion support & consulting  <>  http://producingoss.com/consulting.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jun 2 00:49:29 2007

This is an archived mail posted to the Subversion Users mailing list.