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

Re: Bug: Incorrect lock becuase post-lock fails

From: Clint Lawrence <clint.lawrence_at_gmail.com>
Date: Wed, 2 Jul 2008 23:27:04 +0100

On 02/07/2008, at 12:05 PM, Giulio Troccoli wrote:
> I have already posted this on the users mailing list and someone else
> (Clint Lawrance) was able to reproduce it.
> I myself used SVN 1.4.4, on a RHEL4 box with Apache 2.0 (don't
> think it
> matters though). He said he used the current trunk, I'm not sure about
> the environment.

Yes, I'm certain that this is independent of platform or ra layer etc.

> The problem manifests itself when the post-lock hook fails. The
> file is
> locked but Subversion thinks it's locked in another working copy.

If I understand the hook system correctly, this is no different to any
of the other post-* hooks failing. The server will complete the
operation, run the hook that fails and return an error. The client then
fails to complete its part of the operation due to the returned error.

What makes this case different, is you have no way to recover the lock
in the working copy you're in. For each other operation and
failed post-* hook script, a simple svn update will get your working
back up to date with the server. But if the post-lock fails, the client
will never apply the lock to the working copy.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-07-03 00:27:25 CEST

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

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