From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tobias Geerinckx-Rice via Bug reports for GNU Guix Subject: bug#37386: ungoogled-chromium broken because of openssl update Date: Wed, 11 Sep 2019 23:03:28 +0200 Message-ID: <87d0g6czq7.fsf@nckx> References: <87h85iimov.fsf@jlicht.xyz> Reply-To: Tobias Geerinckx-Rice Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:52245) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i89mW-0006Tx-KL for bug-guix@gnu.org; Wed, 11 Sep 2019 17:04:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i89mV-0004jz-Md for bug-guix@gnu.org; Wed, 11 Sep 2019 17:04:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:34003) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i89mU-0004j5-Je for bug-guix@gnu.org; Wed, 11 Sep 2019 17:04:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i89mU-0002tH-84 for bug-guix@gnu.org; Wed, 11 Sep 2019 17:04:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87h85iimov.fsf@jlicht.xyz> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" Cc: 37386@debbugs.gnu.org, Jelle Licht --=-=-= Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Jelle, Jelle Licht =E5=86=99=E9=81=93=EF=BC=9A > Commit cf065aba1ec14bdacab7a5a6bddbdfd7661cd409 seems to have=20 > broken > node, which subsequently broke ungoogled-chromium. It should=20 > still be > possible to upgrade node to the latest LTS version 10.16.3, but=20 > this > requires an upgrade to the following rebuild-the-world packages: > - libuv > - nghttp2 Yeah, I was just trying to update node but it is indeed not=20 simple. > > What do we do? I'd like to avoid rolling back the openssl update if at all=20 possible. I'll try grafting openssl-next, I guess=E2=80=A6 Kind regards, T G-R --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQT12iAyS4c9C3o4dnINsP+IT1VteQUCXXlhIAAKCRANsP+IT1Vt ef7yAQDvnBblxA9ka2iqWu9ZjIrU4o4l/55PWsEaLP5J9hbrAAEAskAv+iumfoqS A/rPBxrJTSS5bHmVv6wJxT/Tprav5gg= =uqE8 -----END PGP SIGNATURE----- --=-=-=--