Search Criteria
Package Details: tortoisehg 6.9-0
Package Actions
Git Clone URL: | https://aur.archlinux.org/tortoisehg.git (read-only, click to copy) |
---|---|
Package Base: | tortoisehg |
Description: | Graphical tools for Mercurial |
Upstream URL: | https://foss.heptapod.net/mercurial/tortoisehg/thg |
Licenses: | GPL |
Submitter: | bwalle |
Maintainer: | Misery |
Last Packager: | Misery |
Votes: | 126 |
Popularity: | 0.035569 |
First Submitted: | 2011-06-11 12:14 (UTC) |
Last Updated: | 2025-01-16 13:23 (UTC) |
Dependencies (12)
- mercurial (mercurial-hgAUR, mercurial-stable-hgAUR)
- python (python37AUR, python311AUR, python310AUR)
- python-iniparseAUR (python-iniparse-gitAUR)
- python-pyqt5 (python-pyqt5-sip4AUR, python-pyqt5-webkitAUR, python-pyqt5-pre-releaseAUR)
- python-qscintilla-qt5
- qt5-svg (qt5-svg-gitAUR)
- python-build (make)
- python-installer (make)
- python-setuptools (make)
- python-wheel (make)
- python-nautilus (nautilus-python) (optional) – Python binding for Nautilus components
- python-pygments (optional) – syntax highlighting
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 23 Next › Last »
schnedan commented on 2020-01-30 22:59 (UTC)
For me your latest PKGBUILD (28.01.2020) stopped working, again as it seems dependency is to the phyton2 based mercurial, but thg expects python3 instead:
depends=('python' 'mercurial>=5.2.2' 'mercurial<5.3' 'python-qscintilla-qt5' 'python-iniparse' 'qt5-svg' 'python-pyqt5')
also mercurial-python3 currently is 5.2.1, so the requirement for 5.2.2 also fails
... just an additional question, as mecurial-python3 also has some major bugs, e.g. it does not work for me at work with our IT's proxy and TLS breaking malware scanner setup (this is why I currently host a second mecurical for phyton2 on the same machine, so I can at least merge, push and pull), do you see any posibility to provide an python2 based mecurical with a matching tortoisehg until that other stuff is ready for daily work. I would have no problem if that is sort of self contained in /opt and duplicates any needed lib or so - it just should work and not break with normal rolling updates. Don't know the opinion of otheres here, but for me thg is a major productivity tool I use at work, and currently there is no alternate availible. other tools are python2 plus in most cases qt4... and fiddeling with shelfs and mq's by hand is a pain in the ass, right?
chrisjbillington commented on 2019-12-11 14:01 (UTC)
@Artalus no worries, now you can experience the actual bugs tortoisehg has on Python 3 :)
Artalus commented on 2019-12-11 13:51 (UTC)
Oh, my bad! Apparently I was reusing cached build files that were somehow created back with python 3.7. After I cleaned up
yay
cache and reinstalled both packages,thg
started just fine. Cheers!chrisjbillington commented on 2019-12-11 13:37 (UTC)
@Artalus, it definitely shouldn't have installed to python3.7/site-packages - did you have a venv or conda env active when you ran makepkg? If so it would have used the Python interpreter from the venv/conda env. You'll need to deactivate the env (having one active permenently in your shell, as conda does by default, causes all sorts of issues of this nature)
Artalus commented on 2019-12-11 10:22 (UTC)
I installed
mercurial-python3
, but it put all its files in/usr/lib/python3.7/site-packages
instead of/usr/lib/python3.8
. After I created symlinks formercurial
,semver
,iniparse
,hgext
(couldn't create forhgext3rd
sincetortoisehg
package creates the directory for itself), I managed to installtortoisehg
. However when starting it it fails with this traceback:chrisjbillington commented on 2019-11-28 22:20 (UTC)
@schnedan, sorry, I forgot to add the version number to the
provides
array, so pacman didn't acceptmercurial-python3
as satisfyingmercurial>=5.2
. I've fixed it now so you shouldn't have to edit PKGBUILDs anymore.There are still many bugs using tortoisehg under Python 3, looks like you're hitting this one, or something with a similar underlying cause:
https://bitbucket.org/tortoisehg/thg/issues/5491/py3-propertychanged
I don't hit that bug upon simply opening a repo, but I hit something similar looking if I open tortoisehg twice:
https://bitbucket.org/tortoisehg/thg/issues/5479/py3-traceback-upon-starting-workbench
Best you can do for now is report bugs to the bitbucket issue tracker, follow the tortoisehg dev mailing list to see when things are fixed, try to use tortoisehg in a way that avoids hitting the bugs that break things, and use tortoisehg-hg to get the latest commits from the stable branch that fix the bugs.
schnedan commented on 2019-11-28 22:02 (UTC) (edited on 2019-11-28 22:03 (UTC) by schnedan)
Hi, build your mercurial-python3, edited the tortoisehg PKGBUILD, replacing the dependency to mecurial with mecurial-python3... installed fine then. but when running tortoisehg and openning a repository it crashed with this message:
chrisjbillington commented on 2019-11-28 14:50 (UTC)
Until Mercurial built with Python 3 is in the repositories, I've made mercurial-python3, which is the latest released mercurial built with Python 3. It can be used to satisfy the mercurial requirement of this package.
chrisjbillington commented on 2019-11-28 14:28 (UTC) (edited on 2019-11-28 14:36 (UTC) by chrisjbillington)
@sotoleni, the Arch package is still built with Python 2 - you need mercurial 5.2 built with Python 3. You can build the mercurial package from the repos with 5.2 and Python 3 like so:
The
updpkgsums
and---skippgpcheck
are essentially not checking the integrity of the sources at all, so feel free to verify them yourself, but since they are downloaded frommercurial-scm.org
over HTTP I would not be concerned.(Edited out a lot of nonsense from this comment - I thought the repos updated to 5.2, but they didn't, they updated to 5.1.2 which is still "beta" python 3 support)
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 23 Next › Last »