On Oct 29, 2010, at 17:11, Daniel Shahaf wrote: > Short version: it's a bug in Google's backend, and I can reproduce it > with neon but not with serf.
> % $svn log -v -r2967 http://pure-lang.googlecode.com/svn/trunk > --config-option servers:global:http-library=serf > ------------------------------------------------------------------------ > % echo $? > 0 > % $svn log -v -r2967 http://pure-lang.googlecode.com/svn/trunk > --config-option servers:global:http-library=neon > ... > subversion/libsvn_ra_neon/util.c:773: (apr_err=160004) > svn: Observed changes didn't match count > % echo %? > 1 > % ./tools/dev/which-error.py 160004 > 00160004 SVN_ERR_FS_CORRUPT > % $svn --version | head -n2 > svn, version 1.7.0 (dev build) > compiled Oct 27 2010, 15:38:01 > % I agree using serf instead of neon makes the error message go away. But it also doesn't actually show the list of files affected by the commit like it should. See "svn diff --summarize -r2967" for all the files that should be shown there. Also, even when I change http-library to serf in the servers config file, svnsync still shows the "Observed changes didn't match count" error. Does svnsync not use this library setting? >> I'm unsure what we should try from here. Possibly this error is unique >> to Google Code's Subversion backend, > > The error code confirms your suspicion. Furthermore, the word > "Observed" doesn't appear in Subversion's source code. I suppose we should report the problem to Google Code and hope they can uncorrupt the repository somehow? Apparently a couple dozen subsequent revisions see the same error, through r2993.
