mercurial vs >= 3.0 deb for Ubuntu 10.04 64 bit

[Augie Fackler]

> On Apr 14, 2016, at 17:10, Sean Farley <sean at farley.io> wrote:
> 
> 
> Augie Fackler <raf at durin42.com> writes:
> 
>>> On Apr 14, 2016, at 11:54, Arnel <rcl at openmailbox.org> wrote:
>>> 
>>> On 14 April 2016 10:32AM, Augie Fackler wrote:
>>>>> On Apr 13, 2016, at 13:19, Uwe Brauer <oub at mat.ucm.es> wrote:
>>>>> 
>>>>> 
>>>>>> On 13 April 2016 11:12AM, Uwe Brauer wrote:  
>>>>> 
>>>>>> Is building Mercurial from source completely not an option?  
>>>>> 
>>>>> Is is an option, I just had a lot of bad experience upgrading pandoc on
>>>>> Ubuntu 10.04, so I'd prefer a compiled version, but if there isn't any,
>>>>> I have to build it my own, since 1.4.1 I consider far too old.  
>>>> 
>>>> Note that 'make deb' is a thing you can do in any recent (3.7.x certainly) source tree for hg and (assuming you have the right tools installed) it'll drop out a deb for your current OS. It'll even run the tests before it builds the deb.
>>>> 
>>>> (Not sure if that's helpful, but maybe it is?)
>>> 
>>> I tried that around a month ago on an Ubuntu 14.04 machine, and it never worked
>>> for me. Where I was able to get a .deb package from was after running 'sudo
>>> checkinstall'.
>>> 
>>> I'd still like to use it in the future, though. Are there any requirements for
>>> it?
>> 
> 
> On Ubuntu 14.04 and 16.04, I would always get this error:
> 
> Copyright (C) 2005-2016 Matt Mackall and others
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> make[1]: Leaving directory '/home/sean/projects/hg'
> dpkg-buildpackage -rfakeroot -D -us -uc -b
> dpkg-buildpackage: source package mercurial
> dpkg-buildpackage: source version 3.7.3+880-8d398155bfda
> dpkg-buildpackage: source distribution unstable
> dpkg-buildpackage: source changed by Mercurial Devel <mercurial-devel at selenic.com>
> dpkg-source --before-build hg
> dpkg-buildpackage: host architecture amd64
> dpkg-checkbuilddeps: error: Unmet build dependencies: python-all

^ this line is telling you that if you install python-all, it'll be happy.

> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
> dpkg-buildpackage: warning: (Use -d flag to override.)
> debuild: fatal error at line 1376:
> dpkg-buildpackage -rfakeroot -D -us -uc -b failed
> Makefile:165: recipe for target 'deb' failed
> make: *** [deb] Error 29
> 
>> It should just be the tools to give you a compiler and debhelper. I think https://selenic.com/hg/file/tip/contrib/docker/ubuntu-trusty correctly lists the packages you need to install for the build to work.
> 
> Aha! That's what was needed! It seems there were some lint
> errors/warnings?
> 
> dpkg-buildpackage: binary-only upload (no source included)
> Now running lintian...
> E: mercurial changes: bad-distribution-in-changes-file unstable
> W: mercurial-common: embedded-javascript-library usr/lib/python2.7/dist-packages/mercurial/templates/static/excanvas.js please use libjs-excanvas
> W: mercurial-common: manpage-has-errors-from-man usr/share/man/man5/hgrc.5.gz 1313: warning: macro `orig.' not defined
> W: mercurial-common: binary-without-manpage usr/bin/hg-ssh
> E: mercurial-common: wish-script-but-no-wish-dep usr/share/mercurial/hgk
> Finished running lintian.

Yeah, we don't care much about those lintian warnings. The goal is to make it trivial to safely install/distribute builds of hg from tip (eg nightlies), not to have a pedantically correct debian package. :)

> _______________________________________________
> Mercurial mailing list
> Mercurial at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial