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

Unable to lock error: what is going on here?

From: Steve Cohen <scohen_at_javactivity.org>
Date: Wed, 01 Dec 2010 11:42:25 -0600

$ svn update
svn: Unable to lock 'utscmd'

$ svn propget svn:ignore

utscmd is a subdirectory of the current working directory. It is
included in svn:ignore. Why is svn even trying to lock this directory?

The sequence of events here is that the project was checked out and then
its build command run. The build command created a number of
directories, which have been added to svn:ignore so as not to figure in
svn at all.

What am I failing to understand here?

Steve Cohen
Received on 2010-12-01 18:43:49 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.