Subversion is going to try to execute the script as "pre-revprop-change".
Unlike on Windows where file extensions carry such valuable information as
"This can be executed" (.EXE, .COM) and "What kind of program or script is
this" (.BAT versus .EXE), to a Unix-y shell interpreter file extensions mean
nothing. So it's safe (required, even, in Subversion's eyes) to name your
script "pre-revprop-change" -- with no extension -- and include a hint to
the shell interpreter as to which program to use to parse that sucker in the
shebang line (the first line of the script):
#!/bin/sh
# Here's my pre-revprop-change hook script blah blah
# blah...
...
Charan wrote:
> I renamed .tmpl to.sh and also checked the execute permissions but still
> I get the same error.
>
> Thanks
>
> On Mon, Mar 1, 2010 at 12:20 PM, Tyler Roscoe <tyler_at_cryptio.net
> <mailto:tyler_at_cryptio.net>> wrote:
>
> On Mon, Mar 01, 2010 at 12:15:16PM -0800, Charan wrote:
> > I have been trying to edit the already existing log message using
> > TortoiseSVN tool but it is giving me the following error. I can
> see that the
> > file pre-revprop-change hook exists in hook scripts folder with .tmpl
> > extension and it is executable.
>
> Subversion won't exexcute hooks called *.tmpl. Rename the hook script to
> not have that extension and your Subversion server should start using
> it.
>
> tyler
>
>
>
>
> --
> Thanks,
> Charan
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2010-03-01 21:59:19 CET