unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
Cc: 37386@debbugs.gnu.org, Jelle Licht <jlicht@fsfe.org>
Subject: bug#37386: ungoogled-chromium broken because of openssl update
Date: Wed, 11 Sep 2019 23:03:28 +0200	[thread overview]
Message-ID: <87d0g6czq7.fsf@nckx> (raw)
In-Reply-To: <87h85iimov.fsf@jlicht.xyz>

[-- Attachment #1: Type: text/plain, Size: 595 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      reply	other threads:[~2019-09-11 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11 20:48 bug#37386: ungoogled-chromium broken because of openssl update Jelle Licht
2019-09-11 21:03 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0g6czq7.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=37386@debbugs.gnu.org \
    --cc=jlicht@fsfe.org \
    --cc=me@tobias.gr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).