[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: E130003: The XML response contains invalid XML - Follow-up

From: Philip Martin <philip_at_codematters.co.uk>
Date: Fri, 16 Mar 2018 13:44:18 +0000

"NOCERA, ANDY" <an2124_at_att.com> writes:

> I used dump and load to debug the malformed node revision ID. Here
> are my steps and what learned. Looks like the revs' file text: entry
> has a zero instead of size. By just editing the size, verify worked.
> No other change was required. The question is can we correct this
> ourselves without a dump and load?
> db/revs/0/1 /usr/tmp/xrepox/db/revs/0/1
> diff db/revs/0/1 /usr/tmp/xrepox/db/revs/0/1
> 18c18
> < text: 1 76 48 0 ec69809945c46f2bb74e99a3ff7cd917
> ---
> > text: 1 76 48 48 ec69809945c46f2bb74e99a3ff7cd917
> 22c22

That looks like issue 4554


Editing the file is unlikely to work. Later revisons refer to data in
earlier revisions via a byte offset into the earlier file. When you
edit "0" to "48" you have changed the byte offset of all the data beyond
the edit and that breaks the references in all the later files. You
would need to identify all the affected offsets in later files and
modify them, which in turn may lead to more offset changes. You may
need to recompute some checksums as well.

Received on 2018-03-16 14:44:33 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.