GNU bug report logs - #37386
ungoogled-chromium broken because of openssl update

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37386 in the body.
You can then email your comments to 37386 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jelle Licht <jlicht <at> fsfe.org>
To: bug-guix <at> gnu.org
Subject: ungoogled-chromium broken because of openssl update
Date: Wed, 11 Sep 2019 22:48:32 +0200

Commit cf065aba1ec14bdacab7a5a6bddbdfd7661cd409 seems to have broken
node, which subsequently broke ungoogled-chromium. It should still be
possible to upgrade node to the latest LTS version 10.16.3, but this
requires an upgrade to the following rebuild-the-world packages:
- libuv
- nghttp2

What do we do?

Message #8 received at 37386 <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
Cc: 37386 <at> debbugs.gnu.org, Jelle Licht <jlicht <at> fsfe.org>
Subject: Re: bug#37386: ungoogled-chromium broken because of openssl update
Date: Wed, 11 Sep 2019 23:03:28 +0200

[Message part 1 (text/plain, inline)]

Jelle,

Jelle Licht 写道：
> Commit cf065aba1ec14bdacab7a5a6bddbdfd7661cd409 seems to have 
> broken
> node, which subsequently broke ungoogled-chromium. It should 
> still be
> possible to upgrade node to the latest LTS version 10.16.3, but 
> 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 
simple.

>
> What do we do?

I'd like to avoid rolling back the openssl update if at all 
possible.  I'll try grafting openssl-next, I guess…

Kind regards,

T G-R

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.