Inconsistent locks between working copy and repository

------
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 ! )
 
 
 
My first thought has that I have some bug in the pre-commit script.
After some time messing with the script, I found that there is no
error in the pre-commit script, but for some reason, the command
"svnlook lock filaA" informs no lock on the file.
 
So I replace the pre-commit code with this just the one line:
            exit 1
 
The same happened. If the transactiopn fails, but the lock is released.
I attached a shell script for reproduce the problem.
Is something that I don't understand?
If the commit fails why lock is released?
And the worst is that before the end of the transaction
(inside pre-commit hook) the lock is already released.
 
 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org