From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, joseph@lafreniere.xyz
Cc: 38824@debbugs.gnu.org, brettg@gnu.org
Subject: [bug#38824] [PATCH] gnu: mercurial: Update to 5.2.1.
Date: Mon, 06 Jan 2020 18:55:25 +0100 [thread overview]
Message-ID: <87h81831wy.fsf@devup.no> (raw)
In-Reply-To: <87pnfy71dt.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> LaFreniere, Joseph <joseph@lafreniere.xyz> 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.
That seems orthogonal to the discussed patch though, seeing as tests
have been disabled in Mercurial since forever.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-01-06 17:56 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
2020-01-07 21:00 ` Roel Janssen
2020-01-11 1:54 ` bug#38824: " Brett Gilio
2020-01-06 17:55 ` Marius Bakke [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h81831wy.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=38824@debbugs.gnu.org \
--cc=brettg@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.