Package Details: mercurial-hg r49336.290c29df1915-2

Git Clone URL: https://aur.archlinux.org/mercurial-hg.git (read-only, click to copy)
Package Base: mercurial-hg
Description: Distributed source control management tool
Upstream URL: https://www.mercurial-scm.org/
Licenses: GPL2
Conflicts: mercurial
Provides: mercurial
Submitter: Chocobo1
Maintainer: Chocobo1
Last Packager: Chocobo1
Votes: 1
Popularity: 0.000000
First Submitted: 2017-08-25 08:35 (UTC)
Last Updated: 2023-09-12 21:23 (UTC)

Required by (238)

Sources (2)

Latest Comments

lucian commented on 2021-03-03 17:05 (UTC)

update doesnt run through ... on manjaro

ImportError: cannot import name parsers ==> ERROR: Failure while downloading hg hg repo Aborting... Failed to build mercurial-hg

couldnt find solution yet ....

mjacob commented on 2019-11-25 15:09 (UTC)

@Chocobo1 Thank you, great!

Chocobo1 commented on 2019-11-25 03:54 (UTC)

I think that in 95% of the cases, users of this AUR package want the stable branch instead of the default branch.

Maybe so, but then the users are looking at the wrong package. Some users do actually want to work on the default branch, trying the most bleeding edge features and that is exactly what the "-hg" word in package name is all about.

I suppose creating another package targeting stable branch would benefit other users and that would also avoid editing PKGBUILD to adjust target branch. And so I submitted: mercurial-stable-hg.

mjacob commented on 2019-11-24 20:51 (UTC)

The problem was fixed in the meantime: https://www.mercurial-scm.org/repo/hg-committed/rev/640bae94f2f3

@Chocobo1 In any case, I think that in 95% of the cases, users of this AUR package want the stable branch instead of the default branch. The problem wouldn’t have happened with the stable branch. If people know that they want the default branch, it would be easy for them to adjust the PKGBUILD.

Especially for users of TortoiseHg that would be nice, because they need Mercurial to run on Python 3 and the mercurial-hg package provides that, but most likely they want a more stable version of it.

Chocobo1 commented on 2019-11-18 15:59 (UTC)

I got an error: install: cannot stat 'doc/hg.1': No such file or directory Could you confirm?

Same here, seems it is caused by https://www.mercurial-scm.org/repo/hg/rev/2e017696181f. I also find out that it will build successfully if all mercurial/help/ instances are changed to mercurial/helptext/ in "hg/doc/Makefile". This is clearly an upstream error/issue so I would prefer to let them resolve it instead of having a temporary patch here. It is really kind of dumb that they don't test doc generation in their CI pipeline :(

sir_lucjan commented on 2019-11-18 14:45 (UTC)

Hi.

I got an error:

install: cannot stat 'doc/hg.1': No such file or directory

Could you confirm?