GNU bug report logs - #37421
node fails to build during update

Previous Next

Package: guix;

Reported by: sirmacik <sirmacik <at> wioo.waw.pl>

Date: Mon, 16 Sep 2019 08:59:02 UTC

Severity: normal

Merged with 37386, 37407

Done: Tobias Geerinckx-Rice <me <at> tobias.gr>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Tobias Geerinckx-Rice <me <at> tobias.gr>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#37386: closed (ungoogled-chromium broken because of openssl
 update)
Date: Fri, 20 Sep 2019 15:32:03 +0000

[Message part 1 (text/plain, inline)]
Your message dated Fri, 20 Sep 2019 17:31:29 +0200
with message-id <87y2yjugq6.fsf <at> nckx>
and subject line Re: bug#37421: Apply nodejs test workaround?
has caused the debbugs.gnu.org bug report #37421,
regarding ungoogled-chromium broken because of openssl update
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
37421: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=37421
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]
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 part 3 (message/rfc822, inline)]
From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: 37421-done <at> debbugs.gnu.org
Subject: Re: bug#37421: Apply nodejs test workaround?
Date: Fri, 20 Sep 2019 17:31:29 +0200

[Message part 4 (text/plain, inline)]
Jack,

Jack Hill 写道：
> I wanted to ping this issue. From the discussion in #37421, it 
> seems
> like we are OK with disabling the problematic tests as a 
> work-around
> for now.

We are.  Done as aae65db560bd146ba47774cca46056d72be2a5d4 and 
closing.

Kind regards,

T G-R

[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 5 years and 241 days ago.

Previous Next

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