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

> $ 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.

BOb
Received on 2010-12-02 15:40:35 CET