From: Marius Bakke <mbakke@fastmail.com>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: 32095@debbugs.gnu.org
Subject: [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0.
Date: Sat, 22 Sep 2018 17:32:11 +0200 [thread overview]
Message-ID: <875zyxmttw.fsf@fastmail.com> (raw)
In-Reply-To: <87in2x36ys.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
Mathieu Lirzin <mthl@gnu.org> writes:
> Hello,
>
> Mathieu Lirzin <mthl@gnu.org> writes:
>
>> On master, the build failed with libuv 1.19.2, however with libuv 1.21.0
>> both the build and test suite succeed.
>
> Looking at the state of current branches, I think both ‘node’ and
> ‘libuv’ upgrades can pushed on ‘core-updates-next’.
>
> WDYT?
We already have the latest libuv on 'core-updates'. I wanted to push
this patch to master actually (with a libuv-1.23 package), but node does
not work with OpenSSL 1.1.1:
<https://github.com/nodejs/node/issues/18770>.
So I wonder if we should downgrade to the 8.12 LTS release, which still
supports OpenSSL 1.0, until the OpenSSL situation is sorted. From what
I can tell it might take a while.
What do you think?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-09-22 15:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 15:16 [bug#32095] [PATCH 0/2] Update libuv and node Mathieu Lirzin
2018-07-08 15:20 ` [bug#32095] [PATCH 1/2] gnu: libuv: Update to 1.21.0 Mathieu Lirzin
2018-07-08 15:20 ` [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0 Mathieu Lirzin
2018-07-09 14:59 ` Ludovic Courtès
2018-09-06 23:23 ` Mathieu Lirzin
2018-09-07 11:21 ` Marius Bakke
2018-07-09 14:58 ` [bug#32095] [PATCH 1/2] gnu: libuv: Update to 1.21.0 Ludovic Courtès
2018-07-09 15:08 ` Ludovic Courtès
2018-09-07 15:13 ` [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0 Mathieu Lirzin
2018-09-22 15:08 ` Mathieu Lirzin
2018-09-22 15:32 ` Marius Bakke [this message]
2018-09-22 16:36 ` Mathieu Lirzin
2018-09-23 13:22 ` Marius Bakke
2018-09-23 14:03 ` Mathieu Lirzin
2018-09-25 22:45 ` bug#32095: " 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=875zyxmttw.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=32095@debbugs.gnu.org \
--cc=mthl@gnu.org \
/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).