[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-users
Subject:    Re: Fwd: [Linux] Hook hashbang hardships
From:       Branko_Čibej <brane () apache ! org>
Date:       2016-10-12 10:14:44
Message-ID: 5f565b34-2a37-531c-f285-8870d38abeb3 () apache ! org
[Download RAW message or body]

[switching back to users@]

On 12.10.2016 12:04, Dario Niedermann wrote:
> Il 12/10/2016 alle 11:29, Stefan ha scritto:
>
>> Forwarding messages to the dev list is not really considered good
>> practice.
> The community guide on Subversion's website says it's OK to ask on
> dev@ if a report on a possible issue with svn doesn't goes unanswered
> on users@. Considering that the only reply I got on users@ was from
> someone who completely misread the problem, it seemed to me that the
> last-ditch attempt before opening an issue was to report it is dev@.
>
> Returning to the original topic, and just to be even clearer: this is
> about Subversion NOT RUNNING a script because it has a FLAG FOR THE
> SHELL in its SHEBANG LINE. Not because I got the path to bash wrong or
> because there is some other error in my script (as should be *OBVIOUS*
> from my very first email).

How do you know the script isn't running? On the contrary, your report
implies that the script /is/ running and exits with an error code; when
you modified it, it stopped exiting with an error.


> I was asking if not running a script under these circumstances is
> INTENDED BEHAVIOUR for svn or if it might be a BUG IN SUBVERSION.

It has nothing to do with Subversion. Subversion is not responsible for
interpreting the #! line at the beginning of the script; the kernel does
that.

-- Brane
[prev in list] [next in list] [prev in thread] [next in thread]