Re: SVN externals (externals failed, already locked)

Matthew J Fletcher <amimjf_at_sky.com> writes:

> I've been expermenting with SVN externals and found an issue which i
> dont fully understand. My repository is as follows;
>
>
> ------------------
>
> +Play (with and extern to URL "https://swserver:8443/svn/Play/Shared
> Sources" Local Path "Project 3")
>
> - Project 3 (externed)
> -> shared.txt
>
> - Project 2 (with an extern to URL
> "https://swserver:8443/svn/Play/Shared Sources" Local Path "Outstation
> Files")
> -> -> Outstation Files (externed)
> -> -> -> shared.txt
> -> -> unieque.txt
>
> -> Project 1 (with an extern to URL
> "https://swserver:8443/svn/Play/Shared Sources" Local Path "osfiles")
> -> -> osfiles (externed)
> -> -> -> shared.txt
> -> -> unieque.txt
>
> - Shared Sources
> -> shared.txt

I'm having difficulty making sense of that description.

svnadmin create repo
svn co file://`pwd`/repo wc
svn mkdir wc/Play
svn mkdir wc/Play/SharedSources
echo foo > wc/Play/SharedSources/shared.txt
svn add wc/Play/SharedSources/shared.txt
svn mkdir wc/Play/Project1
svn mkdir wc/Play/Project2
svn ps svn:externals '^/Play/SharedSources Outstation' wc/Play/Project1
svn ps svn:externals '^/Play/SharedSources osfiles' wc/Play/Project2
svn ps svn:externals '^/Play/SharedSources Project3' wc/Play
# or maybe one svn:externals on Play
# ^/Play/SharedSources Project3
# ^/Play/SharedSources Project2/Outstation
# ^/Play/SharedSources Project1/osfiles
svn ci -mm wc
svn up wc

echo mod >> wc/Play/SharedSources/shared.txt
svn ci -mm wc
svn up wc

> All the externs work as expected and changes to files in "Shared
> Sources" are reflected across the 3 projects. However when doing an
> update/checkout i get the following error " 'External failed Project
> 3' is allready locked via ."

I don't understand that either. How can the externs "work as expected"
if neither checkout nor update work?

> I suspect that its because i am external'ing not into a seperate
> folder, whereas in "Project 1" and "Project 2" the "Shared Sources" go
> in there own folder. However the externals do work as expected.

-- 
Philip