From users-return-26957-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org Fri Mar 16 13:44:32 2018 Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DAE0F18637 for ; Fri, 16 Mar 2018 13:44:31 +0000 (UTC) Received: (qmail 39072 invoked by uid 500); 16 Mar 2018 13:44:31 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 39038 invoked by uid 500); 16 Mar 2018 13:44:31 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 39023 invoked by uid 99); 16 Mar 2018 13:44:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2018 13:44:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 434221A052D for ; Fri, 16 Mar 2018 13:44:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.502 X-Spam-Level: * X-Spam-Status: No, score=1.502 tagged_above=-999 required=6.31 tests=[KAM_COUK=0.85, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id eYFKRyAXPZbJ for ; Fri, 16 Mar 2018 13:44:26 +0000 (UTC) Received: from know-smtprelay-omc-6.server.virginmedia.net (know-smtprelay-omc-6.server.virginmedia.net [80.0.253.70]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 6BB085F58B for ; Fri, 16 Mar 2018 13:44:25 +0000 (UTC) Received: from localhost ([86.9.48.152]) by cmsmtp with ESMTPA id wpeces7CgT4DJwpeceHauH; Fri, 16 Mar 2018 13:44:18 +0000 X-Originating-IP: [86.9.48.152] X-Authenticated-User: codematters@ntlworld.com X-Spam: 0 X-Authority: v=2.3 cv=NZbIKVL4 c=1 sm=1 tr=0 a=rSjZpmdkpCpLRM02tfIJ4Q==:117 a=rSjZpmdkpCpLRM02tfIJ4Q==:17 a=zQP7CpKOAAAA:8 a=mV9VRH-2AAAA:8 a=AYhhiNbGLbfjFe5joQMA:9 From: Philip Martin To: "NOCERA\, ANDY" Cc: Johan Corveleyn , "users\@subversion.apache.org" Subject: Re: E130003: The XML response contains invalid XML - Follow-up References: <99BCC400E8B6334C91FACA6B284C927D41C2A706@MISOUT7MSGUSRCC.ITServices.sbc.com> Date: Fri, 16 Mar 2018 13:44:18 +0000 In-Reply-To: <99BCC400E8B6334C91FACA6B284C927D41C2A706@MISOUT7MSGUSRCC.ITServices.sbc.com> (ANDY NOCERA's message of "Thu, 15 Mar 2018 22:35:32 +0000") Message-ID: <874llgrv7x.fsf@codematters.co.uk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-CMAE-Envelope: MS4wfMdvW0LrwC5cMFConKPLYxUkNMIcRTdTuxKfjAXQcMNno4hay9bY29g+J56YwX6yAA0IpkeCRD2FLtm/yqciEP1FBwHdyZ0CoESBEjYBs+OK3TK5TczD f3eH80cFCiOJwOhVJGkLqp6MCI5eUP1o0ItCbmaSvQem8UE6jZyLWniG0yKrWcNxIak5nYnSOPCqyVwVzSRpBt+sU77Jj/DA81hjvn/y2oM8muJ5TWEhFD2b "NOCERA, ANDY" 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 https://issues.apache.org/jira/projects/SVN/issues/SVN-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. -- Philip