I'd classify any instance of "APR does not understand this error code"
output in the UI as a bug. And, definitely, if you're interesting in
improving libsvn_ra_serf you should head over to the dev@ list.
Thanks!
Daniel
Joel Low wrote on Fri, May 18, 2012 at 08:07:49 +0800:
> Perhaps this should go to dev@ instead? I'd really like to help improve
> Serf.
>
> Regards,
> Joel
>
> > -----Original Message-----
> > From: Joel Low [mailto:joel_at_joelsplace.sg]
> > Sent: Tuesday, 15 May, 2012 6:30 PM
> > To: Stefan Sperling
> > Cc: Subversion Users' List (users_at_subversion.apache.org)
> > Subject: RE: Serf: Error retrieving REPORT (120105): APR does not
> understand
> > this error code
> >
> > Hi Stefan,
> >
> > > -----Original Message-----
> > > From: Stefan Sperling [mailto:stsp_at_elego.de]
> > > Sent: Tuesday, 15 May, 2012 5:12 PM
> > > To: Joel Low
> > > Cc: Subversion Users' List (users_at_subversion.apache.org)
> > > Subject: Re: Serf: Error retrieving REPORT (120105): APR does not
> > understand
> > > this error code
> > >
> > > On Tue, May 15, 2012 at 11:10:35AM +0800, Joel Low wrote:
> > > > Hello,
> > > >
> > > > I was doing a switch for my Apache HTTPd WC from the 2.2 tag to the
> > > > latest
> > > > 2.4 tag in preparation for building 1.7.5's mod_dav_svn. I am using
> > > > Serf as the RA layer: after a minute or two I get the message in the
> > > > title; I don't get the problem using Neon. I've already done a
> > > > Wireshark capture, so let me know who to email it to if it would help
> > > debugging.
> > > >
> > > > I think I need to disclaim that I am connected to s.a.o from
> > > > Singapore, where there is a transparent HTTP proxy implemented at the
> > > > national level for all HTTP requests being routed out of the country.
> > > > It could be that causing the misbehaviour with Serf.
> > > >
> > > > Thanks in advance.
> > >
> > > There are and were many known problems with the serf-based repository
> > > access layer, which is why neon is still the default in Subversion 1.7.
> > > There is work happening on trunk at the moment to iron out these
> > problems.
> > >
> > > If you report problems with serf, you should mention the exact version
> > > numbers of serf and Subversion you used. Else, it is hard to tell
> whether
> > you
> > > ran into some problem that's already been fixed.
> > [Joel Low] I'm using TortoiseSVN nightly builds (on the 1.7 branch)
> > versions:
> >
> > TortoiseSVN 1.7.99, Build 22899 - 64 Bit -dev, 2012/05/12 15:27:56
> > Subversion 1.7.6, -dev
> > apr 1.4.6
> > apr-utils 1.3.12
> > neon 0.29.6
> > serf 1.0.3
> > OpenSSL 1.0.1c 10 May 2012
> > zlib 1.2.7
> >
> > >
> > > If you're in a position to try an svn client compiled from Subversion's
> > trunk,
> > > and linked against the most recent stable release of serf, that would be
> > help
> > > us identify problems that still need to be fixed before serf can be made
> > the
> > > default for Subversion 1.8.
Received on 2012-05-18 20:47:07 CEST