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 9FFFB10B20 for ; Wed, 30 Apr 2014 10:02:49 +0000 (UTC) Received: (qmail 78127 invoked by uid 500); 30 Apr 2014 10:02:49 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 77382 invoked by uid 500); 30 Apr 2014 10:02:39 -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 Delivered-To: moderator for users@subversion.apache.org Received: (qmail 67649 invoked by uid 99); 30 Apr 2014 09:57:51 -0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of andy.bolstridge@gmail.com designates 209.85.214.190 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-type; bh=NwvjSVXB/kwANogXPI86zFZgL4DhvVscYcfwGZYqmfw=; b=qFxRqMYLMe4IPTyFbAydii7vYLOnUEJX0nShVR3Qdbx+DvpzF7igon1QN0bJyDEwT9 8+6n+xo1O7SDbJs7+elaAZJ2xWK6sYx+MI6IzBpCpOVrq3851uAGLoco/PQpVmykCRVa y8XxhFdOJwTZg6GBeWU1y8RHRHYM9DVHyl5psTrsTLr7O2iL53v31XqZLOD6ypZNQtKE 2dRJY01z+wgWpOIyX8STVM/K1otJVeiQek4gBsMsbFRI6nZWqaip25dfNU/3ZQbmUCzS jKS/FRmtxEE2T+zSt3RuVTzM0MRkt8bNp5QaJewhMYU5lE2UEgf716oMKw6WV3KYgVvj WPBg== X-Received: by 10.140.109.203 with SMTP id l69mr1408qgf.32.1398851843446; Wed, 30 Apr 2014 02:57:23 -0700 (PDT) X-Google-Doc-Id: bd0330a4c0506d85 X-Google-Web-Client: true Date: Wed, 30 Apr 2014 02:57:22 -0700 (PDT) From: Andy Bolstridge To: subversion_users@googlegroups.com Cc: Ryan Schmidt , Subversion Users Message-Id: <9130e8dd-c780-4e7c-9042-4ea167177130@googlegroups.com> In-Reply-To: <4DD4FCD7EDF33549A8F0896AD3A8E1670754BF8A@BNE3-0002EMBX.exchange.server-login.com> References: <4DD4FCD7EDF33549A8F0896AD3A8E167075390DA@BNE3-0001EMBX.exchange.server-login.com> <79BFEEFA-0A5D-432F-A470-C953EBE08B4B@ryandesign.com> <4DD4FCD7EDF33549A8F0896AD3A8E1670754BF8A@BNE3-0002EMBX.exchange.server-login.com> Subject: Re: The XML response contains invalid XML MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_931_24389501.1398851842702" X-Google-IP: 149.126.105.68 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_931_24389501.1398851842702 Content-Type: multipart/alternative; boundary="----=_Part_932_13404811.1398851842703" ------=_Part_932_13404811.1398851842703 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I am seeing the same thing. Here's my problem: I had a sub directory in my repo that contained a library that was 2 levels deep. (eg. directory structure ProjectA/lib/releases) I deleted the lib directory and replaced it with an external that had a slightly different structure (lib/releases/v1) I had problems with the external lib, so I reverted to the previous revision.... and that is where the problems started. The XML problem shows up as an error in the server log (using VisualSVN Server, its in the event log). This reads "Working copy path 'Project/lib/release' does not exist in the repository (404, #160013)." with event log entries "Provider encountered an error while streaming a REPORT response" and "A failure occurred while driving the update report editor". Also, when I try to update, I cannot - it complains that the sub dir (lib) "/lib/release isn't in the same repository as " and refuses to update my working copy to the latest revision (that has the external property removed and the old lib/release directories restored). So I'm stuck having to wipe my WC and re-check it out. I assume this is because the new single .svn is doing a few checks on the contents of the WC and reporting what it sees as inconsistencies when it should be updating to the latest repository structure - and taking changes to externals into account. I have removed the offending directory, hoping that it would then realise it was missing and updating it - but it still fails with the 'not same repo' error described before. Note that trying to revert to get the latest revision doesn't work either - the error reads "the node lib comes from unexpected repository , expected ; if this node is a file external using the correct URL in the external defintion can fix the problem, see issue #4087". (My issue is its not a file external) Cleanup also fails to work - same error as revert. Also update to revision, and revert to revision fails with same 'not same repo' error. So what to do!! thanks, Andy (svn 1.8 - latest TortoiseSVN on the client and last-but-one VisualSVN server, so 1.8.4) ------=_Part_932_13404811.1398851842703 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I am seeing the same thing.

Here's my problem:
<= br>I had a sub directory in my repo that contained a library that was 2 lev= els deep. (eg. directory structure ProjectA/lib/releases)

I deleted = the lib directory and replaced it with an external that had a slightly diff= erent structure (lib/releases/v1)

I had problems with the external l= ib, so I reverted to the previous revision.... and that is where the proble= ms started.

The XML problem shows up as an error in the server log (= using VisualSVN Server, its in the event log). This reads "Working copy pat= h 'Project/lib/release' does not exist in the repository (404, #160013)." w= ith event log entries "Provider encountered an error while streaming a REPO= RT response" and "A failure occurred while driving the update report editor= ".

Also, when I try to update, I cannot - it complains that the sub = dir (lib) "<external repo>/lib/release isn't in the same repository a= s <root of my repo>" and refuses to update my working copy to the lat= est revision (that has the external property removed and the old lib/releas= e directories restored).

So I'm stuck having to wipe my WC and re-ch= eck it out.

I assume this is because the new single .svn is doing a = few checks on the contents of the WC and reporting what it sees as inconsis= tencies when it should be updating to the latest repository structure - and= taking changes to externals into account. I have removed the offending dir= ectory, hoping that it would then realise it was missing and updating it - = but it still fails with the 'not same repo' error described before.

= Note that trying to revert to get the latest revision doesn't work either -= the error reads "the node lib comes from unexpected repository <repo ro= ot>, expected <external repo>; if this node is a file external usi= ng the correct URL in the external defintion can fix the problem, see issue= #4087". (My issue is its not a file external)

Cleanup also fails to= work - same error as revert.

Also update to revision, and revert to= revision fails with same 'not same repo' error.

So what to do!!
thanks, Andy

(svn 1.8 - latest TortoiseSVN on the client and la= st-but-one VisualSVN server, so 1.8.4)
------=_Part_932_13404811.1398851842703-- ------=_Part_931_24389501.1398851842702--