Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of andy.levy@gmail.com designates
 209.85.220.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <OFF61E5381.03538322-ON88257BC4.005E5BE5-88257BC4.005FEA2D@rockwellcollins.com>
References: 
 <OF85179A9B.A26A1BAB-ON88257BC2.007CA057-88257BC2.007DECD3@rockwellcollins.com>
 <OFED5466F1.D0B30953-ON88257BC3.000AB3AC-88257BC3.000AD78E@rockwellcollins.com>
 <CAB84uBWiV+HQPuii6DkGzZ6Tb3ud941Cu+Z0XAUVVY2JKyTnNQ@mail.gmail.com>
 <OFB9DC7991.6A9491C6-ON88257BC3.007D0A8D-88257BC3.007E0A41@rockwellcollins.com>
 <CAB84uBW_-rmGWTLR0Z0NA6P6DXwzkzpiGnVmxuRGQHd2dR0y9A@mail.gmail.com>
 <OFF61E5381.03538322-ON88257BC4.005E5BE5-88257BC4.005FEA2D@rockwellcollins.com>
From: Andy Levy <andy.levy@gmail.com>
Date: Sun, 11 Aug 2013 14:56:58 -0400
Message-ID: 
 <CALb=wnn157UX8XWK44_REngPrRO9-zEJV3JaN9jsHqds8TWW1A@mail.gmail.com>
Subject: Re: Error processing externals E205011 and W155035 with simple update
To: dlellis@rockwellcollins.com
Cc: Johan Corveleyn <jcorvel@gmail.com>,
	"users@subversion.apache.org" <users@subversion.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Aug 11, 2013 at 1:27 PM,  <dlellis@rockwellcollins.com> wrote:
> Johan Corveleyn <jcorvel@gmail.com> wrote on 08/11/2013 03:09:55 AM:
>
>> From: Johan Corveleyn <jcorvel@gmail.com>
>> To: dlellis@rockwellcollins.com
>> Cc: "users@subversion.apache.org" <users@subversion.apache.org>
>> Date: 08/11/2013 03:10 AM
>> Subject: Re: Error processing externals E205011 and W155035 with simple
>> update
>>
>> [ In general, this list prefers bottom-posting (i.e. putting your
>> reply at the bottom) or inline replying. More below ... ]
>
> Roger that!
>
>>
>> On Sun, Aug 11, 2013 at 12:56 AM,  <dlellis@rockwellcollins.com> wrote:
>> > Hi Johan,
>> >
>> > I'll try and use the reproduction template, but will need to work this
>> > on
>> > Monday as it appears I'll need to work the template a bit to work with
>> > http://.
>>
>> I don't think the bug is related to the protocol. From what I've read
>> so far, I think you should be able to reproduce this with file:// just
>> as well (if not: that would be interesting additional information).
>>
>> Note that you can use "repository-relative externals" with ^/ etc, so
>> you don't have to specify the protocol in your externals definition.
>
> Sorry, I wasn't implying that the bug is HTTP related, just that our
> enterprise only allows http access to our SVN repos.  That said, I'm also
> not sure that I can run the template as it appears to require creating a
> clean repo and we, as lowly developers, are not trusted with such power.
>

Create a repository on your workstation and use file:// to access it.
It's only to test/reproduce the issue.