On Tue, Mar 31, 2009 at 4:28 PM, Ben Collins-Sussman
<sussman_at_red-bean.com> wrote:
> Over the last couple of weeks using trunk + serf, I occasionally get
> update failures, and I don't know why. Sometimes they go away,
> sometimes not. Today I tried to update a working copy from a 1.5
> server on red-bean, and I get this perfectly reproducible error:
>
> $ svn up
> subversion/libsvn_ra_serf/update.c:819: (apr_err=175002)
> svn: GET request failed: 400 Bad Request
>
>
> I did a network trace, and while the REPORT request & response seem
> fine, one of the four the subsequent parallelized GET requests is
> making the server throw 400. I can't see why. Can someone take a
> look? I've attached the REPORT response below, followed by the 4 GET
> requests, and then the 400 response.
>
> For some reason, my working copy is of
> http://svn.red-bean.com/repos/sussman/scores/winesburg/kc-score, and
> is now showing up as 'incomplete':
>
> $ svn st
> ! .
> ! vocalscore
> ? vocalscore/15 Elizabeth's Death copy.mus
>
> ... presumably incomplete because every 'svn up' attempt leaves an
> 'incomplete' marker in the entries file. That explains why the REPORT
> request is in cvs-style 'low confidence' mode, where the entire
> entries file is being described.
>
I didn't find root of the problem, but removing '!' character from
X-SVN-VR-Base header value solves the problem. Btw what is Apache
version on red-bean?
--
Ivan Zhakov
VisualSVN Team
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1496585
Received on 2009-03-31 17:06:03 CEST