Re: Commit blocked by pre-commit hook (exit code 255) with no output.

On Fri, Dec 4, 2015 at 11:25 AM, Mark Phippard wrote: > On Fri, Dec 4, 2015 at 11:19 AM, foven wrote: > >> On Thu, Dec 3, 2015 at 8:20 PM, Mark Phippard wrote: >> >>> What I was thinking is that the hook they've installed would have >>> something in it to work in the ssh environment they've con

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

Is SELinux enabled?

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

Guten Tag foven, am Donnerstag, 3. Dezember 2015 um 21:55 schrieben Sie: > AuthorizedKeysCommand /usr/libexec/phabricator-ssh-hook.sh > AuthorizedKeysCommandUser vcs Did you have a look at that script, is it maybe doing more than just authorization? Does it handle svn+ssh different from if you ss

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

On Fri, Dec 4, 2015 at 11:19 AM, foven wrote: > On Thu, Dec 3, 2015 at 8:20 PM, Mark Phippard wrote: > >> What I was thinking is that the hook they've installed would have >> something in it to work in the ssh environment they've configured and be >> able to call your hook as their docs describe

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

On Thu, Dec 3, 2015 at 8:20 PM, Mark Phippard wrote: > What I was thinking is that the hook they've installed would have > something in it to work in the ssh environment they've configured and be > able to call your hook as their docs describe. > > Mark > > Sent from my iPad > > On Dec 3, 2015, a

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

What I was thinking is that the hook they've installed would have something in it to work in the ssh environment they've configured and be able to call your hook as their docs describe. Mark Sent from my iPad > On Dec 3, 2015, at 5:39 PM, foven wrote: > >> On Thu, Dec 3, 2015 at 4:02 PM, Mar

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

On Thu, Dec 3, 2015 at 4:02 PM, Mark Phippard wrote: > Given that you are using Phabricator, have you tried this? > > https://secure.phabricator.com/book/phabricator/article/diffusion_hooks/ > > > > On Thu, Dec 3, 2015 at 3:55 PM, foven wrote: > >> On Thu, Dec 3, 2015 at 2:54 PM, wrote: >> >>>

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

Given that you are using Phabricator, have you tried this? https://secure.phabricator.com/book/phabricator/article/diffusion_hooks/ On Thu, Dec 3, 2015 at 3:55 PM, foven wrote: > On Thu, Dec 3, 2015 at 2:54 PM, wrote: > >> >> On Dec 3, 2015, at 9:40 AM, foven wrote: >> >> On Wed, Dec 2, 201

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

On Thu, Dec 3, 2015 at 2:54 PM, wrote: > > On Dec 3, 2015, at 9:40 AM, foven wrote: > > On Wed, Dec 2, 2015 at 9:50 PM, Nico Kadel-Garcia > wrote: > >> On Wed, Dec 2, 2015 at 2:12 PM, foven wrote: >> >> > I looked at the output of "journalctl -n 50", which seems to be enough >> > to see all th

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

> On Dec 3, 2015, at 9:40 AM, foven wrote: > > On Wed, Dec 2, 2015 at 9:50 PM, Nico Kadel-Garcia > wrote: > On Wed, Dec 2, 2015 at 2:12 PM, foven > wrote: > > > I looked at the output of "journalctl -n 50", which seems to be enough > > to see

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

On Wed, Dec 2, 2015 at 9:50 PM, Nico Kadel-Garcia wrote: > On Wed, Dec 2, 2015 at 2:12 PM, foven wrote: > > > I looked at the output of "journalctl -n 50", which seems to be enough > > to see all that is logged for a commit attempt. I also checked > > /var/log/secure. I didn't see anything tha

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

On Wed, Dec 2, 2015 at 2:12 PM, foven wrote: > I looked at the output of "journalctl -n 50", which seems to be enough > to see all that is logged for a commit attempt. I also checked > /var/log/secure. I didn't see anything that seemed obviously wrong to > me either way, although it is possible

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

On Wed, Dec 2, 2015 at 3:07 PM, Philip Martin wrote: > foven writes: > > > On Wed, Dec 2, 2015 at 11:28 AM, wrote: > > > >> > >> > On Dec 2, 2015, at 9:11 AM, foven wrote: > >> > > >> > Thanks for the reply. > >> > > >> > If the user running the script just needs to have read and execute > >>

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

foven writes: > On Wed, Dec 2, 2015 at 11:28 AM, wrote: > >> >> > On Dec 2, 2015, at 9:11 AM, foven wrote: >> > >> > Thanks for the reply. >> > >> > If the user running the script just needs to have read and execute >> > permission, then if the file has permissions like this: >> > >> > -rwxr-xr

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

On Wed, Dec 2, 2015 at 11:28 AM, wrote: > > > On Dec 2, 2015, at 9:11 AM, foven wrote: > > > > Thanks for the reply. > > > > If the user running the script just needs to have read and execute > > permission, then if the file has permissions like this: > > > > -rwxr-xr-x 1 phd phd 37 Nov 18

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

> On Dec 2, 2015, at 9:11 AM, foven wrote: > > Thanks for the reply. > > If the user running the script just needs to have read and execute > permission, then if the file has permissions like this: > > -rwxr-xr-x 1 phd phd 37 Nov 18 14:39 pre-commit > > shouldn't it work no matter who t

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

Thanks for the reply. If the user running the script just needs to have read and execute permission, then if the file has permissions like this: -rwxr-xr-x 1 phd phd 37 Nov 18 14:39 pre-commit shouldn't it work no matter who the user running the script is? That is how the permissions have

Re: Commit blocked by pre-commit hook (exit code 255) with no output.

On Dec 1, 2015, at 10:30 AM, foven wrote: > I'm configuring Phabricator to host a repository and almost everything > seems to be working. The only issue that I'm currently aware of is > that commits are never successful. Instead the client always gives a > message "svn: E165001: Commit blocked

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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',

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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,

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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

Re: Commit blocked by pre-commit hook (exit code 255) with no output

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