Arch Linux User Repository

@nullstring0 it's because of Arch dropping the required Python Qt Python libraries. They're quite difficult to make AUR packages for since the packages in the repos were restructured in a way that makes it hard to do without conflicts.

I'm not sure why this package uses python3 when the official arch mercurial package is python2.

I changed it back to python2 and it works perfectly fine.

If anyone is interested you can get it here: https://gist.github.com/bjlaur/2ee8a69519e74b9a9a5c8358312dbc14

@schnedan Looking into it, it turns out --partials is an option added to the commit command by the tortoisehg extension, so it is tortoisehg-specific.

So it won't work in the case of using python-mercurial providing the mercurial Python module with mercurial from the repos providing the hg command.

If you really need to have a python2-based hg command, but a python3-based one that tortoisehg can use, then I would recommend:

• installing mercurial-python3 to get everything tortoisehg needs under Python 3: the mercurial python module and the hg command

• Make a custom PKGBUILD for a python2-based mercurial, that renames its executables hg2 etc, and deletes any files that would conflict with mercurial-python3, like man pages and config files.

Then thg would work, and you'd have a hg2 command for your python2-based-mercurial needs

@chrisjbillington I already guessed that tortoisehg executes some commands in a row for quite a lot of things, as I haven't found 1:1 representation of quite some tortoisehg's actions in the hg command set (also for working with mq for example). So you are possibly correct, that it was hg import. But what I did was in the commit mode of tortoise to select some chunks and pressed "commit" [Love that feature and use it qiute a lot]. And with the current version it fails. (solved it again by utilizing my 2nd VM with an older tortoise...) - unfortunally I have no time at work to dig deeper. using arch is just my personal thing, as I like to have modern tools and a compiler which is not several years old....

Can you verify this behavior? If it is a mercurial bug I can report upstream... if not we shouldn't bother the guy's

@schnedan, --partial or --partials isn't an option to commit as far as I can tell. Do you mean --interactive?

--partial is an option for hg import though.

just a Question, if I try to commit chunks, not complete files, I get hg commit option -partials not recognized in the command pane

General mercurial (python3) problem or just "Arch specific?"

@chrisjbillington Thx for your commitment... at least the current setup is the best since the python3 thing started to arrive. Push and Pull now are working in my VM setup! for MQ and shelve I start a 2nd VM with a old Debian, mount via ssh to my repository inside the 1st VM and do the things with a complete python2 tortoisehg :-) ugly but it works.

Update: @j77hm @schnedan, yeah it's totally my fault, this setup doesn't work.

Tortoisehg must be calling the hg executable at some point, and getting the Python2 one which can't import the tortoisehg extensions.

Use mercurial-python3. I'll probably delete python-mercurial ... and maybe make a python2-mercurial if the tools I need aren't ported to Python 3 by the time mercurial on Arch is Python 3 based.

Pretty annoying that it's so hard to have mercurial python libraries coexisting for py2 and py3.

@j77hm @schnedan, this setup of having two mercurials was intended (at least by me, the maintainer of mercurial-python3 and python-mercurial). python-mercurial is the Python libraries only, without the hg command or other executables, so it's supposed to make tortoisehg work without otherwise messing with things. This is so that things requiring a Python 2 based mercurial still work (i.e. hg-fast-export, which I've been using lately in order to evacuate bitbucket as they end mercurial support).

Nonetheless I will investigate if this setup is causing the failed to import extension tortoisehg.util.... errors, as I am seeing them too.

schnedan wrote:

installed mercurial,tortoisehg and python-mercurial

Doesn't that mean you've installed two versions of mercurial? At least one of which is not compatible with tortoisehg?

If I remember right, I uninstalled mercurial and installed only mercurial-python3.