Hi,

I hope I'm not beating a dead horse with that answer, but I recently decided to install mercurial on my N900 and I *seem* to have gotten it to work (at least running 'hg' returns the help text and no python messages about missing packages).

It seems that the post-install script of mercurial_1.4.1-maemo1_armel.deb is broken, because it removes the directories mercurial and hgnext under /usr/lib/python2.5/site-packages/ after being installed, supposedly to eliminate "wrong" packages from mercurial-common_1.4.1-maemo1_all.deb, but by doing this, it also removes the version of those directories it provides itself, so the user is left without any python-modules for mercurial

Anyway, the way I managed to get it to work:
- first install python-dev (omitting this appearently causes the infamous " No module named osutil" error)
- then install the mercurial package (which will install mercurial-common too, as it depends on this package)
- then install the mercurial-common package AGAIN to bring back the site-packages the mercurial postinstall script removed:
If all went well, you should have a functional mercurial installation now (at least as far as I can see, never having used hg before etc. )

It would be nice if the maintainer could fix the package, as I don't really have a clue how to do that, and don't have time atm to dive into the depth of the debian package system...

Regards,
Eagle_Linux