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

Re: Working copy locked after doing a svn:externals

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-08-28 16:49:58 CEST

"Sander van der Wal" <svdwal@mBrainSoftware.com> wrote on 08/28/2006
10:07:25 AM:

> I have a problem with a project that uses an svn:externals property
> In a single repository (I am just testing things out) there is a project
> a sharedproject
> the folder layout is
> project
> trunk
> doc
> group
> sharedproject
> src
> sharedproject
> trunk
> doc
> group
> src
> the idea is that project/trunk/sharedproject links to sharedproject
> svn:externals. So there is a svn:externals property on project/trunk,
> the value "sharedproject svn://host/test/sharedproject". The property
> been set using TortoiseSVN.
> According to the manual, a svn update on 'project' should read
> sharedprojects folders and files into the project/sharedproject folder
> the sandbox. This is not happening, however. I see a
> svn:Working copy 'sharedproject' locked
> svn: run 'svn cleanup' to remove locks(type...)
> Ok, so I run svn cleanup and svn update again, and I get the same error.
> have not locked sharedproject myself, and I haven't touched the svn
> configuration so I woudl expect that there were no locks. svn status
> say anything about locks either.

It sounds like you created an actual folder in your repository named
"sharedproject" that is under "project/trunk". There should not be one.
svn:externals will create it for you in the working copy.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 28 17:17:23 2006

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.