SVN Error: Commit blocked by pre-commit hook (exit code 1) with output: Error: n/a (6)

Question

Some weird error cropped up suddenly outta nowhere and is preventing me from checking in my code via TortoiseSVN. I'm using a free account on myversioncontrol.com

This is on a Windows Vista system. It was working fine till earlier in the day. Any clue how to get things back to normal?

The Tortoise window shows this

Command: Commit  
Modified: ...\edit.php  
Sending content: ...\edit.php  
Error: Commit failed (details follow):  
Error: Commit blocked by pre-commit hook (exit code 1) with output:  
Error: n/a (6).  
Finished!:

score 35 · Answer 1 · answered Sep 14 '09 at 18:57

35

Could it be that you have not entered a commit message? According to their twitter feed: "New functionality added. Block users from committing work without writing a log message. Find in the resources section of your control panel".

answered Sep 14 '09 at 18:57

Stefan

43,293
10
75
117

3

Ignoring the fact that the accepted answer actually solved the OP's problem, this in my experience is the most common cause of the pre-commit hook error. – David Perry May 19 '12 at 00:33
2

Glad I read this answer. I was stuck with this darn error to figure out the server requested a comment. An appropriate error message would have helped :) – Richard Lalancette Oct 10 '12 at 18:04
1

In my case, the problem was "quotes" on message. – rkawano Feb 16 '16 at 19:31
1

Perfect answer you have put a message – Vivek Jul 04 '16 at 15:35

Neil Barnwell · Accepted Answer · 2009-09-14T14:52:31.617

Sounds like myversioncontrol.com have added a pre-commit hook, or have one that is now failing. If it's a free account, it might be you've exceeded some sort of monthly commit or bandwidth limit. Check their terms of service and/or contact them to see what's up.

UPDATE:
I've just checked their website, and it looks like the free account is only valid for 30 days, so you might've exceeded that. You may need to pony up the £3.50pcm or find somewhere else (Google Code is one suggestion, though there are others).

Simon Groenewolt makes a good point that you may have changed something in the control panel on their website that has turned on a pre-commit hook but where it's configured incorrectly.

Thank you Neil, Simon and Stefan - I'm not sure why, but the problem seems to have solved itself. I did mess around with the user-in-question's settings, but that didnt work at that time. Only after a day things got back to normal... ((shrugs)) - oh well! :) — Steve, Sep 15 '09 at 11:48

score 5 · Answer 3 · answered Sep 14 '09 at 14:46

A pre-commit hook is something that runs on the server, so this probably has nothing to do with your local setup. It could be that you changed something in a settings panel on myversioncontrol.com that is implemented using a pre-commit hook or the myversioncontrol people made an error and added a non-functioning hook.

score 5 · Answer 4 · answered Jan 30 '10 at 08:33

5

Sorry for "answering my own question", but I figured out a workaround... If we remove the newlines in the comment / commit message, it seems to work fine.

answered Jan 30 '10 at 08:33

Steve

1,857
5
32
45

1

There are no new lines in my commit message but still it gives error....Any other work-around you could figure out? – Meet Jul 24 '12 at 10:57
In my case it was a "<" in my commit message – achecopar Feb 27 '17 at 19:44
In my case it was "#" this is used for an Assembla tag legitimately but there was additional “#” characters unrelated to the tag mechanism that tripped it – Moon Waxing Aug 24 '18 at 03:07

score 2 · Answer 5 · answered Mar 03 '14 at 19:37

2

This happened to me, and it was caused the absence of a comment (should say "comment required" instead of this enigmatic error at first, right...)

answered Mar 03 '14 at 19:37

Lissandro

71
5

score 1 · Answer 6 · answered Feb 11 '14 at 10:59

1

Recently I am also faced the same problem, while submitting my own WordPress plugin to the directory, Finally, i figured out and worked me,

Just add a comment/ Commit message. It will work,

I used TortiseSVN.

answered Feb 11 '14 at 10:59

varadha

11
2

score 1 · Answer 7 · edited Apr 13 '16 at 07:48

1

If you are getting following exception:

Error: Commit failed (details follow):
Error: Commit blocked by pre-commit hook (exit code 1) with output:
Error: svnlook: Path 'trunk/Development/ProjectName' is not a file

Then first check-in all the the directories and then all the files. It will work.

edited Apr 13 '16 at 07:48

Floern

33,559
24
104
119

answered Apr 13 '16 at 06:49

Hanamant Jadhav

627
7
12

score 1 · Answer 8 · answered May 26 '16 at 05:41

I got the error as, "svn: Commit blocked by pre-commit hook (exit code 1) with output: Failed with exception: Lost connection to MySQL server at 'reading initial communication packet', system error: 104."

I tried 'svn commit' after 'svn cleanup'. And It works fine!.

score 0 · Answer 9 · answered Dec 10 '14 at 16:18

0

you need to add comments and associate with an artifact id with no return key at the end. for example, [artf12345] - your comments.

answered Dec 10 '14 at 16:18

Varadarajan

1

T.Todua · Answer 10 · 2015-03-21T10:25:39.490

0

SOLUTION for WORDPRESS PLUGINS:

I think, get_option() returns FALSE (instead of EMPTY). So, check your plugin. Instead of:

if (empty(get_option('smth')))

there should be:

if (!get_option('smth'))

edited Mar 21 '15 at 10:25

answered Mar 20 '15 at 18:30

T.Todua

53,146
19
236
237

score 0 · Answer 11 · answered Jul 05 '16 at 10:05

I have encounter the same issue and found that i have forgot to prefix the commit message with project identifier. Project identifier is must in our case followed by the commit message. So at the server end it doesn't found the prefix and raised the issue.

score 0 · Answer 12 · answered Nov 19 '18 at 12:57

0

In my case, the solution was to remove "" (quotation mark) from commit message. Weird

answered Nov 19 '18 at 12:57

tourniquet

1,375
2
15
19

SVN Error: Commit blocked by pre-commit hook (exit code 1) with output: Error: n/a (6)

12 Answers12

SOLUTION for WORDPRESS PLUGINS: