On Tue, Nov 05, 2002 at 09:26:42PM +0000, Philip Martin wrote:
> Philip Martin <philip@codematters.co.uk> writes:
>
> Here's the neon output of the 'svn merge' response that's causing the
> invalid XML error
>
...
> ../svn/subversion/libsvn_ra_dav/util.c:332: (apr_err=175002, src_err=0)
> svn: RA layer request failed
> svn: REPORT request failed on /repositories/merge_tests-4/A/B
> ../svn/subversion/libsvn_ra_dav/util.c:316: (apr_err=175002, src_err=0)
> svn: The REPORT request returned invalid XML in the response: XML parse error at line 13: xmlParseStartTag: invalid element name
> .. (/repositories/merge_tests-4/A/B)
>
> I'm assuming the problem is the <D:status>HTTP/1.1 200 OK</D:status>
> line in the middle of the propstat. Is this a server bug?
No, that's correct for a propstat. If you save that XML into a file
(minding line wraps), and run xmllint on it, does xmllint produce the
same parse error? (it parses fine for me, which is weird)
Can you break on ne_xml_parse() in your debugger and check that the data
neon passes to libxml is actually the same as what is being dumped in
the debug output?
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 5 22:47:57 2002