commit with exit code 255
Hello together, a few days ago I set up a subversionserver. Now I wanted to check every commit for some conventions. I tried it with an pre-commit hook but always get the following error when I try to commit something: Some of selected resources were not committed. svn: E165001: Commit failed (details follow): svn: E165001: Commit failed (details follow): svn: E165001: Commit blocked by pre-commit hook (exit code 255) with no output. svn: E175002: MERGE of '/svn/firstrepo/repotest/trunk': 409 Conflict (http://...) Here is the content of my pre-commit script: #!/bin/sh REPOS=$1 TXN=$2 echo something for the output 1>&2 #cancel all commits for tests exit 1 Every user has executerights for the hook. I use svnserver version 1.6.8. Even with disabled firewall I cant commit something (even from the subversionserver itself) What is wrong in my configuration? Thanks for help
Re: commit with exit code 255
On Sun, Jun 17, 2012 at 9:41 AM, Chris Stäbler wrote: > Hello together, > > ** ** > > a few days ago I set up a subversionserver. Now I wanted to check every > commit for some conventions. I tried it with an pre-commit hook but always > get the following error when I try to commit something: > > ** ** > > Some of selected resources were not committed. > > svn: E165001: Commit failed (details follow): > > ** ** > > svn: E165001: Commit failed (details follow): > > svn: E165001: Commit blocked by pre-commit hook (exit code 255) with > no output. > > svn: E175002: MERGE of '/svn/firstrepo/repotest/trunk': 409 Conflict > (http://...) > > ** ** > > Here is the content of my pre-commit script: > > ** ** > > #!/bin/sh > > REPOS=”$1” > > TXN=”$2” > > echo “something for the output” 1>&2 > > #cancel all commits for tests… > > exit 1 > > ** ** > > ** ** > > Every user has executerights for the hook. > > I use svnserver version 1.6.8. > > Even with disabled firewall I can’t commit something (even from the > subversionserver itself) > > ** ** > > What is wrong in my “configuration”? > > Thanks for help > In Bash and in most programming languages, "exit 1" means failure. "exit 0" means success and is probably what you should be using.
Re: commit with exit code 255
On Jun 17, 2012, at 12:10, Nico Kadel-Garcia wrote:
> On Jun 17, 2012, at 08:41, Chris Stäbler wrote:
>
>> a few days ago I set up a subversionserver. Now I wanted to check every
>> commit for some conventions. I tried it with an pre-commit hook but always
>> get the following error when I try to commit something:
>>
>> Some of selected resources were not committed.
>> svn: E165001: Commit failed (details follow):
>>
>> svn: E165001: Commit failed (details follow):
>> svn: E165001: Commit blocked by pre-commit hook (exit code 255) with
>> no output.
>> svn: E175002: MERGE of '/svn/firstrepo/repotest/trunk': 409 Conflict
>> (http://...)
>>
>> Here is the content of my pre-commit script:
>>
>> #!/bin/sh
>> REPOS=”$1”
>> TXN=”$2”
>> echo “something for the output” 1>&2
>> #cancel all commits for tests…
>> exit 1
>
> In Bash and in most programming languages, "exit 1" means failure. "exit 0"
> means success and is probably what you should be using.
Nico, I think Chris knows that. He's trying to verify that a simple test
pre-commit hook script prints the error message he wrote ("something for the
output") and exits with the error code he specified (1). From the output he
showed above, neither is happening; it prints no output, and it exits with code
255. He's asking why that's happening.
Chris, I get the same result as you, if I forget to mark the pre-commit hook
script as executable. So try "chmod 755 /path/to/repo/hooks/pre-commit", then
try again.
Also, not sure if it was a copy/paste error with your email program, but the
script you showed above contains smart quotes (“”); for a bash script, you'll
want to use straight quotes ("").
Re: commit with exit code 255
On Jun 17, 2012, at 15:11, Ryan Schmidt wrote: > Chris, I get the same result as you, if I forget to mark the pre-commit hook > script as executable. So try "chmod 755 /path/to/repo/hooks/pre-commit", then > try again. Oops, I trimmed the part of your message where you said you already tried that: >> On Jun 17, 2012, at 08:41, Chris Stäbler wrote: >> >>> Every user has executerights for the hook. If your Subversion server happens to be running on an operating system with SELinux enabled, there are some additional issues you have to consider; see: http://subversion.apache.org/faq.html#reposperms
Re: commit with exit code 255
On Sun, Jun 17, 2012 at 4:18 PM, Ryan Schmidt < subversion-20...@ryandesign.com> wrote: > > On Jun 17, 2012, at 15:11, Ryan Schmidt wrote: > > > Chris, I get the same result as you, if I forget to mark the pre-commit > hook script as executable. So try "chmod 755 > /path/to/repo/hooks/pre-commit", then try again. > > Oops, I trimmed the part of your message where you said you already tried > that: > > >> On Jun 17, 2012, at 08:41, Chris Stäbler wrote: > >> > >>> Every user has executerights for the hook. > > If your Subversion server happens to be running on an operating system > with SELinux enabled, there are some additional issues you have to > consider; see: > > http://subversion.apache.org/faq.html#reposperms > This is especially true if you've set up your repositories in a conceptually reasonable but non-standard location. The RPM's for RHEL and Fedora, for example, hint at putting repositories in /var/www/svn, which is usually covered by the SELinux rules for /var/www and can help avoid the problems.
*CANNOT* submit patches to d...@subversion.apache.org due to bounces
I've tried repeatedly over the last few days to submit some patches with my gmail account to d...@subversion.apache.org, but they're bouncing with this sort of response: This happened from my home just now, and happened actually sending from the Elego building at the Subversion Hackation last week. Delivery to the following recipient failed permanently: d...@subversion.apache.org Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 552 552 spam score (5.0) exceeded threshold (HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URIBL_BLACK (state 17). Who's got contact with the email hosting services at apache.org?
Re: *CANNOT* submit patches to d...@subversion.apache.org due to bounces
Nico Kadel-Garcia wrote on Sun, Jun 17, 2012 at 16:54:00 -0400: > I've tried repeatedly over the last few days to submit some patches with > my gmail account to d...@subversion.apache.org, but they're bouncing with > this sort of response: This happened from my home just now, and happened > actually sending from the Elego building at the Subversion Hackation last > week. > > Delivery to the following recipient failed permanently: > d...@subversion.apache.org > Technical details of permanent failure: > Google tried to deliver your message, but it was rejected by the recipient > domain. We recommend contacting the other email provider for further > information about the cause of this error. The error that the other server > returned was: 552 552 spam score (5.0) exceeded threshold > (HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URIBL_BLACK (state 17). > > Who's got contact with the email hosting services at apache.org? infrastruct...@apache.org. If you ask them they will just tell you not to send text/html.
Re: *CANNOT* submit patches to d...@subversion.apache.org due to bounces
Daniel Shahaf wrote on Mon, Jun 18, 2012 at 00:21:13 +0300: > Nico Kadel-Garcia wrote on Sun, Jun 17, 2012 at 16:54:00 -0400: > > I've tried repeatedly over the last few days to submit some patches with > > my gmail account to d...@subversion.apache.org, but they're bouncing with > > this sort of response: This happened from my home just now, and happened > > actually sending from the Elego building at the Subversion Hackation last > > week. > > > > Delivery to the following recipient failed permanently: > > d...@subversion.apache.org > > Technical details of permanent failure: > > Google tried to deliver your message, but it was rejected by the recipient > > domain. We recommend contacting the other email provider for further > > information about the cause of this error. The error that the other server > > returned was: 552 552 spam score (5.0) exceeded threshold > > (HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URIBL_BLACK (state 17). > > > > Who's got contact with the email hosting services at apache.org? > > infrastruct...@apache.org. If you ask them they will just tell you not > to send text/html. ... and, on second read, that URIBL_BLACK is also odd --- what URLs did you include in the message?
