Re: Error while committing

Try executing the script directly from the console. You'll have to
approximate the environment that Subversion has when invoking your script.
Perform the action as the correct user (apache?), with the correct working
directory. If that works, then delete all the environment variables, and
try again....

Eric.

On Wed, Dec 17, 2014 at 5:26 AM, Somashekarappa, Anup (CWM-NR) <
anup.somashekarappa_at_rbc.com> wrote:
>
> Hi,
>
> Same script is working fine for other repository.
>
>
> Thanks & Regards,
> Anup T S
>
>
> ------------------------------
> *From:* Branko Čibej [mailto:brane_at_wandisco.com]
> *Sent:* 2014, December, 17 5:59 AM
> *To:* users_at_subversion.apache.org
> *Subject:* Re: Error while committing
>
> On 17.12.2014 11:46, Somashekarappa, Anup (CWM-NR) wrote:
>
>
>
> Hi,
>
> For one of the repository we are getting the below error while committing.
>
> But the same script is working fine for other repositories.
>
> I have given full permission ( chmod 777 pre-commit ) to the script but it
> is not getting executed.
>
>
>
>
> May I know what could be the reason?
>
>
>
> Exit code 255 usually means that a script was not found, or could not be
> executed. There can be many reasons for that; from invalid symbolic links,
> to a missing #! line in the script itself. In any case, you'll have to
> double-check your server and repository setup.
>
> -- Brane
>
> ______________________________________________________________________
>
> This email is intended only for the use of the individual(s) to whom it is
> addressed and may be privileged and confidential.
> Unauthorised use or disclosure is prohibited. If you receive this e-mail
> in error, please advise immediately
> and delete the original message. This message may have been altered
> without your or our knowledge
> and the sender does not accept any liability for any errors or omissions
> in the message.
>
> Emails are monitored by supervisory personnel in jurisdictions where
> monitoring is permitted.
> Such communications are retained and may be produced to regulatory
> authorities or others with legal rights to the information.
>
>