On 4/25/07 10:08 AM, "Mark Phippard" <markphip@gmail.com> wrote:
> On 4/25/07, Steve Bakke <steven.bakke@amd.com> wrote:
>> We have a situation recently where the following sequence occurred:
>>
>> % svn lock dir/file_with_needs_lock
>> % svn rm dir
>> % svn ci dir
>>
>> Now lets say that we create a new directory of the same name and attempt to
>> add it:
>> % mkdir dir
>> % touch dir/file_with_needs_lock
>> % svn add dir
>> % svn status u
>> A 0 dir
>> A O 0 dir/file_with_needs_lock
>>
>> Sure enough, when you run 'svnlook lock <old-repo-path>', it shows the lock
>> that was acquired way back before the committed deletion. We found that we
>> had to use svnadmin to unlock that path in order to clear out the
>> repository.
>>
>> This seems like a bug to me. Why doesn't subversion automatically clear a
>> lock for a file that has a successfully committed deletion?
>
> I am not able to recreate this using either 1.4.3 or trunk.
>
> I am using file:// protocol. Perhaps the server protocol matters?
We were using svn+ssh with svnserve 1.4.0 and svn (client) 1.4.2
-steve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 25 19:30:57 2007