subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Cohen <sco...@javactivity.org>
Subject Re: Unable to lock error: what is going on here?
Date Fri, 03 Dec 2010 02:40:00 GMT
On 12/02/2010 05:24 PM, Bob Archer wrote:
>> On 12/02/2010 08:39 AM, Bob Archer wrote:
>>>> $ 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
>>>
>>>
>>>
>> Yes, that was the problem.  The directory was already versioned and
>> it
>> shouldn't have been.  The build process then came along and
>> destroyed it
>> (including its .svn subdirectory) and made a new one.
>>
>> However, I still don't understand why svn update is designed to
>> fail if
>> unversioned directories are found below it.  Couldn't they just be
>> ignored?
>
> try...
>
> svn up --force
>
> BOb
>
>
>
Thanks, Bob.

Mime
View raw message