From: Brett Gilio <brettg@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: joseph@lafreniere.xyz, 38824@debbugs.gnu.org
Subject: [bug#38824] [PATCH] gnu: mercurial: Update to 5.2.1.
Date: Mon, 6 Jan 2020 02:06:16 +0000 (UTC) [thread overview]
Message-ID: <46bbed98-fc0e-4382-b077-1387c7394dfd@localhost> (raw)
In-Reply-To: <87pnfy71dt.fsf@elephly.net>
Jan 5, 2020 2:30:14 AM Ricardo Wurmus :
>
> LaFreniere, Joseph writes:
>
>
> > I think that for now the options are to
> > 1. continue using Python2 for Mercurial;
> > 2. use Python3 but disable all tests, as Janssen's patch suggests;
> > 3. use Python3 but disable the known-failing tests; or
> > 4. hold off on updating the package until upstream supports
> > Python3 across its entire test suite.
> >
> > Of those three, I am most in favor of the third option. I would
> > be glad to submit a patch that implements it if there is agreement
> > to take that direction.
> >
>
> I agree that option 3 (with a link to the upstream discussion) is the
> right way to go forward.
>
> Thanks!
>
> --
> Ricardo
>
I am also in agreement that working-around the failing tests is the best option, with a backup of just disabling the tests until the python3 incompatibilities are resolved. We need to work away from python2 wherever possible. Since the upstream is aware of the problem I see avoiding python2 as a reasonable alternative to work-arounds.
--
Brett M. Gilio
GNU Guix, Contributor | GNU Project, Webmaster
[DFC0 C7F7 9EE6 0CA7 AE55 5E19 6722 43C4 A03F 0EEE]
<brettg@gnu.org> <brettg@posteo.net>
next prev parent reply other threads:[~2020-01-06 2:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 21:56 [bug#38824] [PATCH] gnu: mercurial: Update to 5.2.1 Roel Janssen
2020-01-03 23:02 ` Brett Gilio
2020-01-04 7:13 ` Roel Janssen
2020-01-05 6:15 ` LaFreniere, Joseph
2020-01-05 8:29 ` Ricardo Wurmus
2020-01-06 2:06 ` Brett Gilio [this message]
2020-01-07 21:00 ` Roel Janssen
2020-01-11 1:54 ` bug#38824: " Brett Gilio
2020-01-06 17:55 ` [bug#38824] " Marius Bakke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46bbed98-fc0e-4382-b077-1387c7394dfd@localhost \
--to=brettg@gnu.org \
--cc=38824@debbugs.gnu.org \
--cc=joseph@lafreniere.xyz \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).