subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philip Martin <philip.mar...@wandisco.com>
Subject Re: Status of 1.7.3
Date Thu, 09 Feb 2012 18:28:36 GMT
Johan Corveleyn <jcorvel@gmail.com> writes:

> The "dangerous behavior" may have been present in 1.7.0 already, but
> 1.7.3 will be the first release where this appeared to cause a real
> issue. I mean, for some reason the bug (or manifestation of the
> "lingering bug") first appeared on 1.7.x after r1239697 (backport of
> r1237720 and r1239596 (stuff in mod_dav_svn/liveprops.c) from trunk).

I've managed to reproduce the problem on my Linux box using a different
dataset.  Using r1239696, i.e. before the revision that triggers the
regression test FAIL on your machine, I see:

$ rm -rf repo && svnadmin create repo && \
  svnrdump dump -r840000:head http://localhost:8080/repos/asf \
  --config-option servers:global:http-library=serf | svnadmin load repo
     * adding path : subversion/trunk/ac-helpers/gnu-diff.sh ... done.
svnadmin: E140001: Unrecognized record type in stream
svnrdump: E135007: Write error in pipe

A second run gives:

svnadmin: E185003: Delta does not fill the target window
     * adding path : subversion/trunk/www/project_nav.html ...svnrdump: E135007: Write error
in pipe

I get similar errors when I switch my server to mod_dav_svn 1.6.

So the problem is simply that svnrdump doesn't work with serf.

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com

Mime
View raw message