On 4/10/06, Michalis Karatzas <michalis.karatzas@gmail.com> wrote:
> ------
> setup
> ------
>
> I setup a svn repository accessible throw apache2 http for the
> needs of a project.The project has a lot of binary files so we
> end up using the Lock/Modify/Unlock mode and this lead me to
> write some hook scripts to force the users to work in that mode
> (e.g. All file in the repository has to have a needs-lock
> property set, every change on the repository must be on files
> locked by the transaction owner, etc)
> All the svn clients access the repository throw http and apache2
>
>
> ------------
> The problem:
> ------------
>
>
> A repository user locks a file ( fileA ) and moves to fileB:
> >svn lock fileA
> >svn move fileA fileB
>
>
> So far all is ok.
>
>
> When the user commits the changes and the pre-commit fails, so
> the transaction fails, the locks between the working copy and
> the repository are inconsistent. ( e.g. the lock on
> the fileA at repository have been released ! )
I just tried to reproduce this here, and it looks like a bug to me.
If you could file an issue that would be great. Note that it doesn't
require apache + mod_dav_svn, you can get the same behavior with
ra_local.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 11 00:03:46 2006