From: Mathieu Lirzin <mthl@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 32095@debbugs.gnu.org
Subject: [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0.
Date: Sat, 22 Sep 2018 18:36:18 +0200 [thread overview]
Message-ID: <87h8ihbibh.fsf@gnu.org> (raw)
In-Reply-To: <875zyxmttw.fsf@fastmail.com> (Marius Bakke's message of "Sat, 22 Sep 2018 17:32:11 +0200")
Marius Bakke <mbakke@fastmail.com> writes:
> We already have the latest libuv on 'core-updates'.
Indeed, I forgot to prune old branches and get confused.
> 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>.
I have read rapidly this thread.
IIRC the build for node 10.xx was failing with ‘openssl’ which was the
reason of upgrading to ‘openssl-next’ and this issue seems to imply that
node fails to run with ‘openssl-next’? Is that correct?
Have you recently tried to compile ‘node’ with libuv-1.23 without
upgrading the “openssl” input? How did it work?
> 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?
I think that ideally it would be a good idea to have both the latest and
the LTS versions distributed in Guix. So I agree with your solution of
downgrading to 8.12 LTS.
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
next prev parent reply other threads:[~2018-09-22 16:41 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
2018-09-22 16:36 ` Mathieu Lirzin [this message]
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=87h8ihbibh.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=32095@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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).