On Wed, Feb 22, 2012 at 9:06 AM, Philip Martin <philip.mar...@wandisco.com> wrote:
>>> Update a different subtree: >>> >>> $ svn up wc/X/Y/Z >>> Updating 'wc/X/Y/Z': >>> A wc/X/Y/Z/Q >>> Updated to revision 4. >> >> This does not work for me. I have an entire repository checked out >> and started an update in my /branches folder and my /trunk folder. >> The latter fails: > > Yes /branches and /trunk will both attempt to lock / to allow for the > target to be deleted. You should be able to update /branches/foo and > /trunk/subversion. Just to clarify. I had two Terminal windows open. In one of them, I was in the /branches/2.3.x folder and ran svn up. In the other, I was in the /trunk folder and ran svn up. This is the one that failed and the error message said: svn: E155004: Working copy '/Users/markphip/work/svnedge' locked. subversion/libsvn_wc/wc_db.c:10690: (apr_err=155004) svn: E155004: '/Users/markphip/work/svnedge/branches' is already locked. svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) Why did it lock the folder above /branches if /branches is the parent of what I was updating? -- Thanks Mark Phippard http://markphip.blogspot.com/
