From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60916) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g3ju6-00037v-1K for guix-patches@gnu.org; Sat, 22 Sep 2018 11:33:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g3ju2-0004HM-Qo for guix-patches@gnu.org; Sat, 22 Sep 2018 11:33:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:45517) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g3ju2-0004HH-MJ for guix-patches@gnu.org; Sat, 22 Sep 2018 11:33:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g3ju2-00057Y-Fl for guix-patches@gnu.org; Sat, 22 Sep 2018 11:33:02 -0400 Subject: [bug#32095] [PATCH 2/2] gnu: node: Update to 10.6.0. Resent-Message-ID: From: Marius Bakke In-Reply-To: <87in2x36ys.fsf@gnu.org> References: <20180708152009.28002-1-mthl@gnu.org> <20180708152009.28002-2-mthl@gnu.org> <87muv0fo9d.fsf@gnu.org> <87pnxqus5x.fsf@gnu.org> <87a7oteeos.fsf@fastmail.com> <87tvn1z6ge.fsf@gnu.org> <87in2x36ys.fsf@gnu.org> Date: Sat, 22 Sep 2018 17:32:11 +0200 Message-ID: <875zyxmttw.fsf@fastmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Mathieu Lirzin Cc: 32095@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mathieu Lirzin writes: > Hello, > > Mathieu Lirzin 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 =E2=80=98node=E2= =80=99 and > =E2=80=98libuv=E2=80=99 upgrades can pushed on =E2=80=98core-updates-next= =E2=80=99. > > 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: . 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? --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlumYHsACgkQoqBt8qM6 VPpQXgf/WdTTr86MQe1LLfPMYI1cEtjrXr7sVvmi4nEcpc7gJdV3PwjkRXRdgKhB OjlIHPBtbGExogzVkT0+TcE9qeBdY/ppnEdwYjkiBxUVa1rNnH8tu2aJMeHWmi2Y uJZq0t5V1MlxpFDQkZ2zOtHLdZrm1jjdXKAfEErm2R+GIlL+VyL30jDGOVmiM89d HMnM5PdFzC5Hjie0iquUbcyRzXQakx0EnaooBFLYiH0k2PCMSsdxvNeXfqYOVnr6 caPbK8fQ4KM8HFX3Fod+RGnRG99b++rjImYViQp/dbVlsvspQC/Ka8OCixqQY3MI U6oAhhn7QDFawq1V8oxUoqXvA5jKDQ== =WgCr -----END PGP SIGNATURE----- --=-=-=--