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

Re: svn:externals - svn: E200009: Targets must be working copy paths

From: Andreas Mohr <andi_at_lisas.de>
Date: Thu, 31 Jan 2013 03:29:21 +0100

Hi,

On Wed, Jan 30, 2013 at 04:38:05PM -0600, Ryan Schmidt wrote:
>
> On Jan 30, 2013, at 14:14, C M wrote:
>
> > Thank you for the "teach a man to fish" approach. Though I didn't find the documentation to be very clear, I was able to set the property using the syntax below.
> >
> >
> > c:\Temp\800>svn propset svn:externals "ver_1.0 svn://3.x.x.x/trunk/Customer1/system_800/ver_1.0" .
> > property 'svn:externals' set on '.'
> >
> > This worked for the directory listed above. I then added several external definitions, but when I finally committed and checked out, it seems that only the last definition was applied. Evidently I overwrote the previous definitions.
> >
> > Can I add multiple external definitions? If it's in the "svn help propset", I am not seeing it.
>
> Yes you can have multiple externals definitions, one on each line of the svn:externals property. Setting a multiline property on the command line via "svn propset" is difficult, so instead try "svn propedit svn:externals ." (and type the multiline externals into the interactive editor) or "svn propset svn:externals --file X ." (and provide a file X containing the multiline externals).

"didn't find the documentation to be very clear",
"I am not seeing it." - perhaps provide useful details of what went wrong in
docs, and then someone sufficiently authorized could ensure
to get that fixed soon?
Otherwise the next Clueless To Be Enlightened Person (tm) [nothing
against the OP, mind you!] comes along and experiences the very same
unspeakable trouble again...

So much for the "teach a man to fish" errmm "teach a document to educate"
approach...

HTH,

Andreas Mohr
Received on 2013-01-31 03:29:56 CET

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.