Ubuntu 16.04 can't compile latest changeset on default branch
Uwe Brauer
oub at mat.ucm.es
Fri Jan 31 18:17:14 UTC 2020
>>> "MK" == Marcin Kasperski <Marcin.Kasperski at mekk.waw.pl> writes:
>> So the simple question is: can I compile it with python2.7 and if I can,
>>
>> how do I configure the Makefile or any other relevant to take 2.7. I
>> can't find anything relevant in the Makefile.
> In general, yes. Of course Mercurial supports 2.7.
> Normal make uses PYTHON environment variable to let you decide.
> In `make deb` case it looks like somebody switched default to py3.
> Take a look at
> contrib/packaging/debian/rules
> (in mercurial sources). Those two lines are responsible:
> export HGPYTHON3=1
> export PYTHON=python3
> Remove first of them, change second to
> export PYTHON=python
> and you should build fine.
Thanks very much,
I looked in that file and hg annotate tells me this
changeset: 43310:7574ccd87200
branch: stable
user: Denis Laxalde <denis at laxalde.org>
date: Mon Oct 21 10:59:54 2019 +0200
files: contrib/packaging/debian/control
contrib/packaging/debian/rules
tests/test-debian-packages.t
description:
packaging: upgrade Debian packaging to build with Python 3
Also drop the explicit "Depends: python" as debhelper will add it.
That explains it thanks very much! I just tried it out, it works.
What would be the problem to return to python 2.7?
Would it make mercurial slower?
In any case thanks
Uwe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5673 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20200131/7b44e338/attachment.p7s>
More information about the Mercurial
mailing list