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

Re: Deadlock on Post-Commit Script

From: Daniel Becroft <djcbecroft_at_gmail.com>
Date: Mon, 24 Aug 2009 19:27:45 +1000

On Mon, Aug 24, 2009 at 6:51 PM, Jake Stone <jake.the.stone_at_gmail.com>wrote:

> Hello!
> I am running SVN over Apache on Windows Server 2003, and I am trying to
> create a post-commit script for an ArgoUML repository. The repository
> only holds their ".zargo" files, and there is a nice command-line method
> to generate SVG diagrams from their UML projects, and I want to create a
> hook to do so automatically.
> I've created a checkout on the SVN server, but when I add "svn update
> %REPOS%" to my post-commit hook, any commits to that repository
> complete, but the post-commit hangs indefinitely. When I cancel the
> commit, the server's checkout requires svn cleanup and svn update to
> properly bring it up to date.

My response was going to be "svn update cannot be run on a repository path",
until I read the rest of your post-commit script.

> I'm sure that running an svn update on a repository you've just
> committed to CAN work, since this person does it here:
> http://blog.pengoworks.com/index.cfm/2008/2/5/SVN-postcommit-for-Windows
> So I'm not sure what the problem is. Removing the svn update portion of
> the hook allows it to run properly. Any ideas what could be causing this?
> Incidentally, if there's a better way to be doing this, like querying
> SVN directly for the latest copies of files rather than keeping my own
> checkout, please let me know.
> Attached is the hook script, though there's nothing else interesting.
> Thanks in advance for your help!

<snipped />

Have you tried just running the "svn update" in the post-commit hook (ie
without any of the transformation steps)?

If you're modifying versioned files within the checked-out working copy, you
could be hitting some sort of conflict, which is triggering the interactive
conflict resolution.

You could try modifying the "svn update" call to use either
"--non-interactive", or one of the variants of the "--accept" switch
("theirs-full" is probably the most likely).

Daniel B.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-24 11:28:50 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.