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!:   

Solution 1

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.

Solution 2

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".

Solution 3

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.

Solution 4

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.

Solution 5

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...)

View more solutions