On 4/11/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> 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
>
thank you Garrett for the reply.
I spend some more time on this and
i wondering if there are two bugs here:
1. Inside pre-commit script the "svnlook lock" or "svnadmin lslocks"
does not list the lock on the file.
2. In case of using ra_dav, after the unsuccessful commit
the lock is released form the repository.
Can please anyone try to reproduce the second one, so I can be sure
before I file those issues?
Thanks a lot,
michalis
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 12 10:46:13 2006