Subscribe to RSS

MERGE request failed on ‘/path/to/file’

After upgrading my Subversion server to Ubuntu Feisty, I noticed that when committing I got the following error:

svn: MERGE request failed on '/svn/repository/trunk'
svn: MERGE of '/svn/repository/trunk': 200 OK (http://svn.myserver.com)

Although the messages says that the commit failed, it has not. A simple ’svn update’ will merge the changes you made to the repository to your working copy again and you’re good to go.

So, what is the problem here? Are you by any chance running Trac? Did you install the post-commit hook to integrate Subversion with Trac? Right, so did I.

The problem here is that the trac-post-commit-hook script needs a few updates in order to include the proper modules. Take a look at the most recent 0.10.x version.

After updating the trac-post-commit-hook script, commits worked fine again. Such an easy fix for such a nasty problem.

Please share the love of this post by bookmarking it, and sharing it with others. Thanks!

  • Digg
  • del.icio.us
  • description
  • Reddit
  • Technorati
  • BlinkList
  • E-mail this story to a friend!
  • Facebook
  • Live
  • MisterWong
  • Netvouz
  • NewsVine
  • Slashdot
  • SphereIt

4 Comments

  1. anonim
    Posted 18 September, 2007 at 17:26 | Permalink

    Thanks dude. I had the same error and I had no clue on how to fix it.

    Thanks again

  2. Posted 16 January, 2008 at 21:44 | Permalink

    Thanks for posting this, as it helped us pinpoint our related problem. To help people with their detective work on similar issues:

    svn: MERGE request failed on ‘/svn/repository/trunk’
    svn: MERGE of ‘/svn/repository/trunk’: 200 OK (http://svn.myserver.com)

    Notice the second line: 200 OK. That means that the actual commit went through ok, which led us to believe our issue had to do with our post-commit hook. We are not using trac’s post-commit hooks, but instead our own, which had an issue with wget. So if you get that error, I would suggest you run svnserve and try to checkout/commit via that, because it will give you a better error message to diagnose the issue.

  3. Posted 6 June, 2008 at 09:55 | Permalink

    Man! Thank you. You stopped a herd of wild developers from hanging me. :)

  4. Gaetan Lauff
    Posted 11 July, 2008 at 19:43 | Permalink

    Thank you for this.
    You saved me from getting tarred and feathered :-)

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*