> From: Max Bowsher [mailto:maxb@ukf.net]
>
>
> Joram Agten wrote:
> > I'm using TSVN 1.0.8, svn 1.06 and svn 1.1.0 rc2 windows binaries.
> > TSVN uses neon 0.24.7, the other two use also at least
> 0.24.7 I guess
> > I turned compression off on the client side (in the
> registry) and tried
> > again
> >
> > svn: REPORT request failed on '/repos/live/!svn/bc/1243/trunk'
> > svn: The REPORT request returned invalid XML in the
> response: XML parse
> > error
> > at line 5035: not well-formed (invalid token)
> > (/repos/live/!svn/bc/1243/trunk)
> >
> > maybe important to know
> > server apache/2.049(win32) svn/1.06 dav/2 php/4.3.7 mod_python/3.1.3
> > python/2.3.3
> > client svn/1.06
> >
> > if I turn off compression, the error message comes at
> exactly the same
> > place,
> > so this does not seem to have any influence.
> > It might be that there are strange characters in the log messages
> > (backspaces
> > mainly) but again, a svnlook on the server works nicely
>
> You could try adding the following to %APPDATA/Subversion/servers:
>
> [global]
> http-compression = no
> neon-debug-mask = 130
>
> or merge it with an existing [global] section if there is one.
>
> Then run the command, capturing stderr to a file:
>
> svn .... 2>errors
>
> The XML response will be printed in the errors file. Examine
> it around the
> indicated line, to see if you can find the ill-formed bit.
>
> Max.
>
I tried this debug mask with svn-1.06 and svn-1.1-rc2 but I get debug logging
so I tried the following
c:\>svn log -v --xml
then I get the following error
svn: Can't write to stream: Not enough storage is available to process this command.
c:\>svn log -v --xml > log.xml
works better, but gives me the same error as earlier. Looking at that line of the xml reveals no error at all.
But I don't know if this is the same xml data as the svn-client processes to generate the error, I suspect it is not.
Received on Wed Sep 8 12:23:02 2004