[PATCH 3 of 6] packaging: upgrade Debian packaging to build with Python 3

Martin von Zweigbergk martinvonz at google.com
Mon Oct 21 23:05:41 EDT 2019


Yuya, are you okay with this patch as it is?

On Mon, Oct 21, 2019, 14:11 Martin von Zweigbergk <martinvonz at google.com>
wrote:

> Sounds good. I'd like to queue this series for stable, but I'll give Yuya
> a chance to comment first.
>
> On Mon, Oct 21, 2019 at 1:48 PM Antonio Muci via Mercurial-devel <
> mercurial-devel at mercurial-scm.org> wrote:
>
>>
>> On 21/10/19 21:52, Augie Fackler wrote:
>> > On Mon, Oct 21, 2019 at 09:30:27AM -0700, Martin von Zweigbergk via
>> Mercurial-devel wrote:
>> >> On Mon, Oct 21, 2019 at 9:21 AM Gregory Szorc <gregory.szorc at gmail.com
>> >
>> >> wrote:
>> >>
>> >>> On Mon, Oct 21, 2019 at 6:57 AM Yuya Nishihara <yuya at tcha.org> wrote:
>> >>>
>> >>>> On Mon, 21 Oct 2019 12:00:55 +0200, Denis Laxalde wrote:
>> >>>>> # HG changeset patch
>> >>>>> # User Denis Laxalde <denis at laxalde.org>
>> >>>>> # Date 1571648394 -7200
>> >>>>> #      Mon Oct 21 10:59:54 2019 +0200
>> >>>>> # Node ID 09f95d7a20c6d2e0bf6218e2a5bc9cd2b803c8ec
>> >>>>> # Parent  70764c9ddba397fa6cc2c92a28a1a65c5bdddaea
>> >>>>> packaging: upgrade Debian packaging to build with Python 3
>> >>>>>
>> >>>>> Also drop the explicit "Depends: python" as debhelper will add it.
>> >>>> So, are we ready to ship py3 version as stable?
>> >>>> I know it's planned for 5.2, but I have no idea about the current
>> state.
>> >>>>
>> >>> We ideally produce Python 2 and Python 3 package variants. Then we
>> switch
>> >>> to Python 3 exclusive in a future release.
>> >>>
>> >>> For Debian packaging, this could be a bit more difficult, as I believe
>> >>> we'd need to fork the Debian packaging templates in the repository.
>> >>>
>> >>> I doubt the in-repo Debian packaging is used that much. So I could go
>> >>> either way with regards to transitioning the packaging to Python 3
>> >>> exclusive. Definitely safer to hold off.
>> >>>
>> >> I suspect they're just used only by Google and I think we're fine with
>> >> internally working around any issues we run into when we switch to py3
>> >> (including backing out these patches).
>> > I believe they have at least some small usership outside Google, as a
>> > way for users to have a more recent hg installed without having to
>> > wait forever for a backport to show up.
>> > _______________________________________________
>> > Mercurial-devel mailing list
>> > Mercurial-devel at mercurial-scm.org
>> > https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
>>
>> I can confirm. The in-repo packaging scripts fill well this need for us.
>>
>>
>> _______________________________________________
>> Mercurial-devel mailing list
>> Mercurial-devel at mercurial-scm.org
>> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20191021/aba0aa4e/attachment.html>


More information about the Mercurial-devel mailing list