On Sun, Aug 11, 2013 at 1:27 PM, <dlel...@rockwellcollins.com> wrote: > Johan Corveleyn <jcor...@gmail.com> wrote on 08/11/2013 03:09:55 AM: > >> From: Johan Corveleyn <jcor...@gmail.com> >> To: dlel...@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, <dlel...@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.
