svnserve 1.2.3 does not run hook scripts

[Sascha Kratky <kr...@unisoftwareplus.com>]

Hi,

I am running svnserve 1.2.3 under Mac OS X 10.3.9. svnserve is  
started via xinetd and seems to work OK.
However, I cannot get svnserve to execute hook scripts. I've set up a  
test post-commit hook script that simply outputs its arguments to the  
console:

#!/bin/sh
echo >/dev/console $0 $1 $2

The script is saved in the hooks directory of the repository under  
the name "post-commit" and has the read and executable bit set for  
the svn user.
When I commit a new version to the repository the script does not  
seem to be run, i.e., no output appears in the console.
The script works as expected if I run it as "env - ./post-commit"  
from the command line.

Is there something else that I can check?

Thanks,
Sascha


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svnserve 1.2.3 does not run hook scripts

[Sascha Kratky <kr...@unisoftwareplus.com>]

Thanks,

the problem seems to be related to OS X 10.3.9. I've tried the same  
subversion setup on another machine running Mac OS X 10.4.5 and the  
hook script seem to work there.

Sascha

On 01.03.2006, at 17:50, Ryan Schmidt wrote:

> On Mar 1, 2006, at 14:46, Sascha Kratky wrote:
>
>> I am running svnserve 1.2.3 under Mac OS X 10.3.9. svnserve is  
>> started via xinetd and seems to work OK.
>> However, I cannot get svnserve to execute hook scripts. I've set  
>> up a test post-commit hook script that simply outputs its  
>> arguments to the console:
>>
>> #!/bin/sh
>> echo >/dev/console $0 $1 $2
>>
>> The script is saved in the hooks directory of the repository under  
>> the name "post-commit" and has the read and executable bit set for  
>> the svn user.
>> When I commit a new version to the repository the script does not  
>> seem to be run, i.e., no output appears in the console.
>> The script works as expected if I run it as "env - ./post-commit"  
>> from the command line.
>
> Interesting idea with the console. Never occurred to me. It works  
> for me with Subversion 1.3.0 on Mac OS X 10.4.5 PPC with a  
> repository accessed via the file:// protocol. So that gives you  
> several things to try, to narrow down the problem: upgrade  
> Subversion to 1.3.0 (a good idea anyway); access your repo via  
> file:// instead of svn://; upgrade Mac OS X.
>
> And before you get into all that, you didn't say if you're doing  
> this already or if you tried this, but try letting any user read  
> and execute the post-commit hook (chmod 755 post-commit).
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svnserve 1.2.3 does not run hook scripts

[Ryan Schmidt <su...@ryandesign.com>]

On Mar 1, 2006, at 14:46, Sascha Kratky wrote:

> I am running svnserve 1.2.3 under Mac OS X 10.3.9. svnserve is  
> started via xinetd and seems to work OK.
> However, I cannot get svnserve to execute hook scripts. I've set up  
> a test post-commit hook script that simply outputs its arguments to  
> the console:
>
> #!/bin/sh
> echo >/dev/console $0 $1 $2
>
> The script is saved in the hooks directory of the repository under  
> the name "post-commit" and has the read and executable bit set for  
> the svn user.
> When I commit a new version to the repository the script does not  
> seem to be run, i.e., no output appears in the console.
> The script works as expected if I run it as "env - ./post-commit"  
> from the command line.

Interesting idea with the console. Never occurred to me. It works for  
me with Subversion 1.3.0 on Mac OS X 10.4.5 PPC with a repository  
accessed via the file:// protocol. So that gives you several things  
to try, to narrow down the problem: upgrade Subversion to 1.3.0 (a  
good idea anyway); access your repo via file:// instead of svn://;  
upgrade Mac OS X.

And before you get into all that, you didn't say if you're doing this  
already or if you tried this, but try letting any user read and  
execute the post-commit hook (chmod 755 post-commit).



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org