No, the person is not using Tortoise SVN. It might have been that
another user was doing something in that branch at the same time that
someone else had the repository locked. I wonder if it is a bug in
Subcommander. I will test the latest beta version.
Thanks,
Mark
Blair Zajac wrote:
> Mark Eramo wrote:
>> Hello,
>> Anyone using Subcommander 1.2.2.1 that experiences intermittent
>> locking issues (Windows Version). I have a user running subcommander
>> in Windows that runs into locks on the repository that I do not have
>> running subcommander under Linux.
>>
>> I figured I would post here as I am not sure if this is a
>> subcommander issue or a subversion issue or just normal. If the user
>> removes the files/folders under the working copy folder and checks
>> out the code again to the working folder, the lock goes away.
>>
>> This started last week when I implemented a post-commit script to
>> send an email to specific users when code was checked in. I have
>> since removed the file from the hooks folder.
>> When I did that, the problem cleared up for me.
>>
>> I am running Subversion 1.4.3
>
> Does the person have TortoiseSVN installed? That can run background
> updates and grab svn working copy locks, which may interfere with
> other clients.
>
> Regards,
> Blair
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 11 16:06:46 2007