A quick check list:
* use both pre- and post-commit hooks: the pre- script checks the
message is valid, the post- script performs the action. Consider the
pair of scripts, not a single one
* double check the permission of the script files: can they be
executed by the web server? svn usually runs as an Apache module, so
the "user" that runs Apache needs read and execute permissions on
these scripts
* check your web server log files for any error message
* did you check that the Python interpreter can be found and run from
the shell scripts?
* did you check that your Trac installation can be found from the
python hook scripts?

HTH,
Manu


On 7/25/06, Rob Wilkerson <[EMAIL PROTECTED]> wrote:
I like to think I'm not usually this thick-headed, but I'm just not
quite getting this.  I have a script in /usr/share/doc/trac/contrib/
called "trac-post-commit-hook.gz".  Opening that, I see the script
details and move to /var/svn/myprojectname/hooks/.  I copy
post-commit.tmpl --> post-commit and paste the code to kick off the
hook script as copied from the comments in the hook itself.

Still nothing.  Do I need to restart any services?  Do I need to do
something else?  What am I missing here?  I've read the svn book on
scripts, but I'm not finding it all that helpful.  There just isn't
much there.

Thanks for your patience.

On 7/24/06, Noah Kantrowitz <[EMAIL PROTECTED]> wrote:
> Look in the subversion book for info on seting up post-commit-hooks. It
> varies slightly from one platform to another, but they go through it in
> detail.
>
> --Noah
>
> Rob Wilkerson wrote:
> > Still isn't working.  I tried your (FIxes #2) syntax both before and
> > after marking the ticket fixed, but nothing was added to the ticket.
> > I didn't "install" any post-commit-hook, though.  Is this natively
> > available or do I have to do this manually?  If so, how?
> >
> > On 7/24/06, Emmanuel Blot <[EMAIL PROTECTED]> wrote:
> >> > wrong.  I include "ticket:2" in the commit message and the ticket
> >> > isn't updated.  I tried marking the ticket fixed both before and after
> >> > committing the change.
> >>
> >> You want to use the following syntax:
> >>
> >> Refs #2 some free message
> >> or
> >> Fixes #2 some free message
> >>
> >> Do not add text before the "refs" or "fixes" keywords.
> >>
> >> HTH,
> >> Manu
> >> _______________________________________________
> >> Trac mailing list
> >> [email protected]
> >> http://lists.edgewall.com/mailman/listinfo/trac
> >>
> >
> >
>
> _______________________________________________
> Trac mailing list
> [email protected]
> http://lists.edgewall.com/mailman/listinfo/trac
>


--

Rob Wilkerson
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac



--
Manu
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac

Reply via email to