[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0.
From: |
Marius Bakke |
Subject: |
[bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0. |
Date: |
Sat, 22 Sep 2018 17:32:11 +0200 |
User-agent: |
Notmuch/0.27 (https://notmuchmail.org) Emacs/26.1 (x86_64-pc-linux-gnu) |
Mathieu Lirzin <address@hidden> writes:
> Hello,
>
> Mathieu Lirzin <address@hidden> 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?
signature.asc
Description: PGP signature
- [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0., Mathieu Lirzin, 2018/09/06
- [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0., Marius Bakke, 2018/09/07
- Message not available
- [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0., Mathieu Lirzin, 2018/09/07
- [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0., Mathieu Lirzin, 2018/09/22
- [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0.,
Marius Bakke <=
- [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0., Mathieu Lirzin, 2018/09/22
- [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0., Marius Bakke, 2018/09/23
- [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0., Mathieu Lirzin, 2018/09/23
- bug#32095: [PATCH 2/2] gnu: node: Update to 10.6.0., Marius Bakke, 2018/09/25