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

Re: svn commit still holds locks when server-side post-commit runs

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Thu, 04 Sep 2008 11:32:36 -0400

Markus Kuhn wrote:
> I am using svn 1.4.4 (SUSE Linux 10.3) with a server-side post-commit
> hook script that (under some circumstances) calls an svn update in the
> same working directory in which I executed the svn commit. In that case,
> I get an error message from the svn update, complaining that it cannot
> acquire locks on the working directory.

Yeah, don't do that. ;-)

You can fork the update (and sleep a second or two) to allow the client
to finish, but it is really a Very Bad Idea(TM) to have server-side
updates firing into the same WC as the commit came from. That usually
means your workflow process is sub-optimal.

> Shouldn't "svn commit" have released all its locks on the working
> directory by the time the post-commit script is executed on the server?

No, because commit isn't complete until the server returns from the
post-commit hook. QED


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-04 17:33:09 CEST

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.