From: Jelle Licht <jlicht@fsfe.org>
To: 37386@debbugs.gnu.org
Subject: bug#37386: ungoogled-chromium broken because of openssl update
Date: Wed, 11 Sep 2019 22:48:32 +0200 [thread overview]
Message-ID: <87h85iimov.fsf@jlicht.xyz> (raw)
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?
next reply other threads:[~2019-09-11 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 20:48 Jelle Licht [this message]
2019-09-11 21:03 ` bug#37386: ungoogled-chromium broken because of openssl update Tobias Geerinckx-Rice via Bug reports for GNU Guix
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h85iimov.fsf@jlicht.xyz \
--to=jlicht@fsfe.org \
--cc=37386@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.