Re: Can't check out http://svn.freebsd.org/base/stable/9/sys/dev/usb/controller with serf

Attila Nagy <bra_at_fsn.hu> writes:

> I'm using subversion 1.7.2 with serf 1.0.0 on FreeBSD to check out
> http://svn.freebsd.org/base/stable/9/sys/dev/usb/controller, but it
> fails at:
> bootvm# svn co http://svn.freebsd.org/base/stable/9/sys/dev/usb/controller
> A controller/atmegadci_atmelarm.c
[...]
> A controller/uhci.h
> svn: E175009: XML parsing failed: (207 Multi-Status)
>
> With neon, the checkout succeeds.

I can reproduce that. The server is sending:

HTTP/1.1 207 Multi-Status\r
Date: Mon, 30 Jan 2012 14:17:15 GMT\r
Server: Apache/2.2.19 (FreeBSD) mod_ssl/2.2.19 OpenSSL/0.9.8q DAV/2 SVN/1.6.17\r
Vary: Label\r
Content-Length: 1396\r
Content-Type: text/xml; charset="utf-8"\r
\r
<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:" xmlns:ns0="DAV:">
<D:response xmlns:S="http://subversion.tigris.org/xmlns/svn/" xmlns:C="http://subversion.tigris.org/xmlns/custom/" xmlns:V="http://subversion.tigris.org/xmlns/dav/" xmlns:lp1="DAV:" xmlns:lp3="http://subversion.tigris.org/xmlns/dav/" xmlns:lp2="http://apache.org/dav/props/">
<D:href>/base/!svn/bln/230302</D:href>
<D:propstat>
<D:prop>
<S:eol-style=native>xhci.h</S:eol-style=native>
<S:keywords=FreeBSD=%H>xhci.c</S:keywords=FreeBSD=%H>
<S:mime-type=text/plain>xhci.h</S:mime-type=text/plain>
<lp1:resourcetype/>
<lp1:getcontentlength>0</lp1:getcontentlength>
<lp1:getcontenttype>text/plain</lp1:getcontenttype>
<lp1:getetag>"230302//stable/9/sys/dev/usb/controller"</lp1:getetag>
<lp1:creationdate>2012-01-18T07:57:17.471381Z</lp1:creationdate>
<lp1:getlastmodified>Wed, 18 Jan 2012 07:57:17 GMT</lp1:getlastmodified>
<lp1:version-name>230302</lp1:version-name>
<lp1:creator-displayname>hselasky</lp1:creator-displayname>
<lp3:md5-checksum>###error###</lp3:md5-checksum>
<lp3:repository-uuid>ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f</lp3:repository-uuid>
<D:supportedlock>
<D:lockentry>
<D:lockscope><D:exclusive/></D:lockscope>
<D:locktype><D:write/></D:locktype>
</D:lockentry>
</D:supportedlock>
<D:lockdiscovery/>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>

and I'd guess that the ###error### in the checksum is the problem.

-- 
Philip