On Apr 15, 2012, at 4:54 PM, Armando Perico wrote:
> I actually don't have an apache user running, however, when I run it
> manually, the script works fine, am I missing anything ?
Of course you do! Otherwise, how could a file be "owned" by user "apache"?
Check the /etc/passwd file. There's
On Sun, Apr 15, 2012 at 4:56 PM, Armando Perico wrote:
> I'm under linux and double checked for windows CRLFs.
> I turned SELinux off ... the error continues
And you can log in and execute it as the apache user? If apache
doesn't have a login shell, start as root and 'su -s /bin/bash -
apache',
I'm under linux and double checked for windows CRLFs.
I turned SELinux off ... the error continues
On Sun, Apr 15, 2012 at 11:38 PM, Les Mikesell wrote:
> On Sun, Apr 15, 2012 at 3:46 PM, Armando Perico wrote:
> > SELinux is off.
> > +x has been set.
> > #!/bin/sh seems ok for me.
>
> Can you ex
On Sun, Apr 15, 2012 at 3:46 PM, Armando Perico wrote:
> SELinux is off.
> +x has been set.
> #!/bin/sh seems ok for me.
Can you execute it directly?Having a Windows style CRLF line
ending on the #!/bin/sh line might prevent it from working and be hard
to see. Otherwise, if you can execute
SELinux is off.
+x has been set.
#!/bin/sh seems ok for me.
I will check the FAQ, however, from what I read around, the pre-commit
script is not even being executed, so I figured it would be uncessary to
debug it. Previously I meant to debug the SVN execution...
I will keep trying here, but pleas
If I understand your pre-commit script, it consists of two lines and can only
exit with a status of 0. Exit 255 code usually means that your script couldn't
get executed.
• You're on Linux or Unix.
• Script is in the hooks directory
• The whole repository is owned apache:apache. And that's the
That error usually means the #! line is bad, or the +x bit is missing,
something like that. Perhaps SELinux (if enabled) can cause similar
effects?
BTW: if you haven't done so already, please read the FAQ entry on
debugging hooks.
Armando Perico wrote on Sun, Apr 15, 2012 at 22:07:31 +0200:
> so
sorry about the cc, my bad.
I really don't know what else to do... I tried a lot already.
Would be nice to be able to debug it better (like a call stack or
something), but the message bellow is all I managed to get.
* svn: Commit blocked by pre-commit hook (exit code 255) with no output
On Sun,
Both of these look normal. Please keep the list in the CC.
Armando Perico wrote on Sun, Apr 15, 2012 at 22:00:41 +0200:
> # xxd pre-commit
> 000: 2321 2f62 696e 2f73 680a 6563 686f 2022 #!/bin/sh.echo "
> 010: 6865 6c6c 6f22 2031 3e26 3220 0a65 7869 hello" 1>&2 .exi
> 020: 7420 300a
Remember that the only output is
From STDERR and only if your script returns a nonzero exit code. What language
in your hook script written in? Do you have the standard pre-commit hook call
your pre-commit?
What OS are you using?
Check to make sure your script is executable and owned by the cor
What's the output of
xxd pre-commit
ls -dl testrepo/hooks/
Armando Perico wrote on Sun, Apr 15, 2012 at 13:02:35 +0200:
> Hello,
>
> I'm having problems with hook scripts (pre-commit or post-commit)
> - When I try to commit, the svn commit is not performing completely, it
> is returning "Commit
Hello,
I'm having problems with hook scripts (pre-commit or post-commit)
- When I try to commit, the svn commit is not performing completely, it
is returning "Commit blocked by pre-commit hook (exit code 255) with no
output"
It passed a long while that I am trying to fix this problem without
hav
12 matches
Mail list logo
