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

Re: SVN externals (externals failed, already locked)

From: Matthew J Fletcher <amimjf_at_sky.com>
Date: Tue, 20 Mar 2012 22:09:12 +0000

On 13/03/12 18:07, Matthew J Fletcher wrote:
> Hi,
>
> 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
>
> ---------------------
>
> 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 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.
>
> I am using subversion 1.7.4 (same on server), via TortoiseSVN.
>

Hi,

Has anyone tried to do this before and encountered this problem ? or can
offer some advice on this usage of externs.

regards

- Matthew J Fletcher
Received on 2012-03-20 23:09:53 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.