Reception error code: 255 when clicking on Mercurial repo from the Eclipse plugin

Question

I use HgEclipse here: http://www.javaforge.com/project/HGE

I created a new repository on my server to test the plugin. I cloned the repository, added some files, committed and tried to click, but received the following error message ...

abort: HTTP Error 500: Internal Server Error. Command line: /home/james/workspace/project:hg -y push http://***@[repository location], error code: 255 

From some Googling, I can find that the 255 error is related to authentication, but the password is correct, otherwise I would not be able to clone in the first place.

Any help or suggestions would be greatly appreciated.

thanks

EDIT : After upgrading my system to the latest versions, I also get this from the command line on click (which previously worked):

 abort: HTTP Error 500: Permission denied: .hg/store/data/path-to-file.i 

Answer 1

Your web server cannot write to the repository. You can either

• change permissions in the local repo so that the web server receives write permissions there (which means that you need to configure write permissions with chmod for all files and directories under (and including) .hg, you also need to set sticky -bit for all directories)
• provide the web server with its own repo, which belongs to the server.

Providing a web service for your own repo is as follows:

 $ sudo bash # mkdir /srv/repo-base # chown www-data /srv/repo-base # cd /srv/repo-base # su -c "hg clone /path/to/current/repo web-repo-name" www-data # vi /etc/apache2/sites-available/$SITE_CONFIG_FILE # change the repo path to /srv/repo-base/web-repo-name # /etc/init.d/apache2 reload 

The disadvantage of this method is that you need to push through http even on a machine with a web server, because, as a regular user, you do not have write permissions to the web server repository.

Answer 2

This is the answer to this for me, although it is a different configuration system: TortoiseHg.
In Repository Settings -> Server I set Allow Push to *
It was on a private network that was protected behind a firewall.