Re: [Linux] Hook hashbang hardships

2016-10-14 Thread Branko Čibej
On 14.10.2016 14:58, Andrew Reedick wrote:
>> Hello! I've been having trouble getting my own pre-revprop-change hook 
>> script to work. Svn was refusing any change to a revprop with the following 
>> error:
>> 
>> svn: E165001: Revprop change blocked by pre-revprop-change hook (exit code 
>> 1) with no output.
>> 
>>
>> Until I found out that the issue was in the script's shebang:
>>
>>  #!/bin/bash -e
>>
>> which wouldn't work. Had to remove ' -e'. Is this expected behaviour or is 
>> there something wrong with svn (version 1.9.4 (r1740329) on
>> Linux/x86_64) ?
>
> Bash doesn't appear to have a "-e" option.  (There is a "-e" test to check if 
> a path exists, but that's not a command line arg you pass in to bash.)
>
> /bin/bash --help
> man bash
> https://linux.die.net/man/1/bash


You really need to read the manpage, which says:

All  of  the   single-character  shell  options  documented  in the
description of the *set* builtin command can be used as options when
the shell is invoked.


-- Brane


RE: [Linux] Hook hashbang hardships

2016-10-14 Thread Andrew Reedick

> Hello! I've been having trouble getting my own pre-revprop-change hook script 
> to work. Svn was refusing any change to a revprop with the following error:
> 
> svn: E165001: Revprop change blocked by pre-revprop-change hook (exit code 1) 
> with no output.
> 
>
> Until I found out that the issue was in the script's shebang:
>
>   #!/bin/bash -e
>
> which wouldn't work. Had to remove ' -e'. Is this expected behaviour or is 
> there something wrong with svn (version 1.9.4 (r1740329) on
> Linux/x86_64) ?


Bash doesn't appear to have a "-e" option.  (There is a "-e" test to check if a 
path exists, but that's not a command line arg you pass in to bash.)

/bin/bash --help
man bash
https://linux.die.net/man/1/bash



Re: [Linux] Hook hashbang hardships

2016-09-27 Thread Ralph Seichter
On 27.09.2016 12:59, Dario Niedermann wrote:

> I found out that the issue was in the script's shebang:
>
> #!/bin/bash -e
>
> which wouldn't work. Had to remove ' -e'. Is this expected behaviour or
> is there something wrong with svn (version 1.9.4 (r1740329) on
> Linux/x86_64) ?

Why would anything be wrong with Subversion? Apparently something is not
going as expected in your own script, causing bash to exit.

Scripts always have to be adapted to local needs. On some systems, the
path for bash might be different, or bash might not be available at all.
That's each user's own responsibility.

-Ralph