Arch Linux User Repository

@ecognito Yep, I'm seeing them too. Could be this: https://bugs.archlinux.org/task/66887

edit: Sorry, just realised I'm linking you to your own bug report!

Further edit: My tracebacks don't seem to be about qscintilla. Otherwise very similar to yours. This is updating to a commit: https://pastebin.com/J9m2kAkB

Anybody else having thg core dump after updating qt5-base and related packages from 5.14.2 to 5.15.0? Here is my stacktrace: https://pastebin.com/d5LLdZET

Thanks @Misery, done!

@chrisjbillington Thanks! I updated the package. Should still work with your 5.3.2. You can upgrade. :-)

@Misery, mercurial 5.4 is out, but I'm holding off pushing a new mercurial-python3 since this package requires < 5.4.

tortoisehg have tagged 5.4rc0, but not a final 5.4 release. Whenever you update this package (whether you decide to go for the release candidate or wait), if you post a comment here letting me know, I'll push the new mercurial-python3 (unless the hg in the repos finally goes to Python3 of course).

I see now. I've been holding back removing python-qscintilla-qt5-common forever because it's required by python2-qscintilla-qt5.

That's probably the only reason this still works on my machine.

@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