[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Inconsistent locks between working copy and repository

From: Madan U S <madan_at_collab.net>
Date: 2006-04-12 11:17:41 CEST

On Wed, 12 Apr 2006 14:14:54 +0530,
> Michalis Karatzas
> <michalis.karatzas@gmail.com> wrote:
>
> 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?

I tried to reproduce it....

I did...
1) svn lock file
2) svn info
 lists, among other info....
 Lock Token: opaquelocktoken:a599b17e-
3811-0410-ae9b-9039c9c8b1da
 Lock Owner: madan
 Lock Created: 2006-04-12 15:00:48 +0530
 (Wed, 12 Apr 2006)
3) modify file
4) svn ci file -m "comment", says...
 Sending trags/file
 Transmitting file data .svn: Commit
failed (details follo
w):
 svn: 'pre-commit' hook failed with
error output:
5) svn info
 <doesnt list the lock info>
However, when I try to lock the file
again,
6) svn lock file
svn: warning: Path '/trags/file' is
already locked by user 'madan' in
filesystem '/tmp/repos-test/db'
 
So, I think the lock is NOT released
from the repository, even though the
working copy seems to have lost the
information about the lock itself.
 
Regards,
Madan.
Received on Wed Apr 12 11:19:20 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.