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

RE: Unable to lock error: what is going on here?

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Thu, 2 Dec 2010 09:39:55 -0500

> $ svn update
> svn: Unable to lock 'utscmd'
> $ svn propget svn:ignore
> utspkg_src
> utscmd
> utslib
> utsbin
> utstool
> 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?

Are you sure utscmd is not already versioned. Ignores only works on non-versioned files.

Received on 2010-12-02 15:40:35 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.