Hook script rights and wrongs...

Just a note here...

I was trying to set a revprop. I typed and got the following:

Z:\@Projects\@Comcast\@TransSVN\jpx\trunk>svn propset "transsvn:bad.prop"
--revprop -r HEAD "My Property"
https://ccpdev2.comcastonline.com/repos/transsvn_testing_REPOS/trunk/
svn: DAV request failed; it's possible that the repository's
pre-revprop-change hook either failed or is non-existent
svn: At least one property change failed; repository is unchanged

I had tried with HEAD, and with the number of the latest revision. No joy.

Server version: 1.2.0, Solaris
Client version: 1.2.1, WinXP

I finally gave the docs a good once over, and copied the
pre-revprop-change.tmpl to pre-revprop-change, and chmoded 774. Still no
joy. Then I chomoded 775, and all was well.... except the fact that
security-wise, "other" now has the execute bit. Is there a reason that
hookscripts need to be executable by anyone to run properly? The ls -la is:

-rwxrwxr-x 1 jogrady apache 2.0K Aug 24 10:21 pre-revprop-change*

...and I would figure that the svn process would be run by the web-dav
process, which is kicked by Apache, which has full rights to the script
already. I know SVN runs the scripts sans env, but is it running them as
another user?

As always, keep up the good work. We're loving it here...

  - John O'Grady
    Senior Software Architect
    Comcast Online

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 24 16:41:21 2005