Re: Deadlock on Post-Commit Script

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

> Answering a few questions from both responses:
>
>
> 1. Ryan: Yes, I am the same user in the hook script as the
> command-line.
> 2. Ryan: Well, if I really can't get the update to work, speed won't be
> a big issue; the repository is a few smaller files (total < 1MB).
> 3. Daniel: what are the "transformation steps" you refer to? All my
> script does is set some variables then run the svn update of which you
> speak.
> 4. Daniel: I'm not modifying any files in the checkout, I only want to
> use update/export to have the latest copy of files to run something else on
> (which does not modify the files either.)
>
> I will try adding --non-interactive and post the results later.
> Thanks for your help!
>

I was referring to the steps involving the creation of the .svg files.
However, I now see that those are commented out.

You could run 'svn status' and 'svn status -u' (although I think the latter
might hang as well) to help identify if conflicts will arise.

The other obvious question I guess, is are you committing from a different
WC that the one that is being updated through the commit hook?

Cheers,
Daniel B.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2386856

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-27 00:06:40 CEST