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

Re: Error processing externals E205011 and W155035 with simple update

From: <dlellis_at_rockwellcollins.com>
Date: Sun, 11 Aug 2013 10:27:39 -0700

Johan Corveleyn <jcorvel_at_gmail.com> wrote on 08/11/2013 03:09:55 AM:

> From: Johan Corveleyn <jcorvel_at_gmail.com>
> To: dlellis_at_rockwellcollins.com
> Cc: "users_at_subversion.apache.org" <users_at_subversion.apache.org>
> Date: 08/11/2013 03:10 AM
> Subject: Re: Error processing externals E205011 and W155035 with simple
> [ 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_at_rockwellcollins.com> wrote:
> > Hi Johan,
> >
> > I'll try and use the reproduction template, but will need to work this
> > 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.

> > Here's the quick recipe....
> >
> > Create a file external in svn:externals and commit it and perform full
> > update (foo.c rev 1).
> Please give the exact value you put into the property. There are a
> couple of variants of the syntax, and it's not clear whether you use a
> peg revision etc.

This is what SVN reports from an svn pg svn:externals before and after the

http://test/pd_sandbox/plcm/swdb/Temp/1.txt@2818 1.txt
http://test/pd_sandbox/plcm/swdb/Temp/1.txt@2827 1.txt

This issue appears if I either use TSVN to enter the above to enter the
local path, URL, and peg revision OR if I programatically perform this
through command line SVN as in :
svn propset svn:externals -F "tmp81A7.tmp" "C:\Project_files\test" where
the contents of the tmp file are:

http://test/pd_sandbox/plcm/swdb/Test/project.conf@2728 project.conf
http://test/pd_sandbox/plcm/swdb/Temp/6.txt@2633 6.txt
http://test/pd_sandbox/plcm/swdb/Temp/7.txt@2626 7.txt
http://test/pd_sandbox/plcm/swdb/Temp/1.txt@2827 1.txt
http://test/pd_sandbox/plcm/swdb/Temp/commit.vbs@2814 commit.vbs
http://test/pd_sandbox/plcm/swdb/Temp/checkintest.txt@2812 checkintest.txt

What is really interesting (to me at least), is that SVN appears to think
the file is then switched (shows S with an svn info 1.txt)

 c:\Project_files\Test>svn status -v --depth immediates

               2851 2851 dlellis .
     S 2851 2827 dlellis 1.txt

> > Create a new revision of the file and commit (foo.c rev 2)
> > Edit the svn:externals to point to latest revision (foo.c rev 2)
> And the exact syntax of the new value.
> >
> > Now here's the magic to reproduce the issue:
> > ;:
> > Only perform an "svn update . -depth empty --ignore-externals" // this
> > should bring in the new svn:externals property with foo.c rev 2
> > Only update the file as "svn update foo.c"
> >
> > This should now show the file as being switched with an "svn status -v
> > foo.c":
> >
> > Performing a full "svn update" will cause the errors and seem to put
the WC
> > into a bad state.
> --
> Johan

Received on 2013-08-11 19:28:19 CEST

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.