GNU bug report logs - #53414
[PATCH] update Node LTS to 16.13.2

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 53414 in the body.
You can then email your comments to 53414 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: zamfofex <zamfofex <at> twdb.moe>
To: "guix-patches <at> gnu.org" <guix-patches <at> gnu.org>
Subject: [PATCH] update Node LTS to 16.13.2
Date: Fri, 21 Jan 2022 12:11:25 -0300 (BRT)

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

Hello, everyone! In case this might be useful, I spent some time updating the Node LTS package to version 16.13.2, which is currently the latest LTS.

I hope this patch is sensible! Please let me know if there is anything I should work on regarding it.

[0001-gnu-node-lts-Update-to-16.13.2.patch (text/x-patch, attachment)]

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

From: "code <at> ceephax.com" <code <at> ceephax.com>
To: 53414 <at> debbugs.gnu.org
Subject: [PATCH] update Node LTS to 16.13.2
Date: Wed, 23 Feb 2022 13:13:26 +0000

This works for me, though i'd prefer it wouldn't replace the previous LTS version as it hasn't reached end of life https://nodejs.org/en/about/releases/

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

From: Maxime Devos <maximedevos <at> telenet.be>
To: "code <at> ceephax.com" <code <at> ceephax.com>, 53414 <at> debbugs.gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 12:07:19 +0100

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

code <at> ceephax.com schreef op wo 23-02-2022 om 13:13 [+0000]:
> This works for me, though i'd prefer it wouldn't replace the previous LTS version
> as it hasn't reached end of life https://nodejs.org/en/about/releases/

It will be end-of-life in two months.  More generally, I don't see the
appeal of packaging old versions, especially old versions that will
soon be unsupported, when there are newer versions (16.X.Y) that will
be supported for a relatively long time (two years).

Also, a question for zamfofex: do the existing node packages still
build, or are there (new) build failures after the patch?

Greetings,
Maxime.

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

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

From: "code <at> ceephax.com" <code <at> ceephax.com>
To: "Maxime Devos" <maximedevos <at> telenet.be>, 53414 <at> debbugs.gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 11:24:45 +0000

On Fri, 25 Feb 2022, at 11:07, Maxime Devos wrote:
> code <at> ceephax.com schreef op wo 23-02-2022 om 13:13 [+0000]:
>> This works for me, though i'd prefer it wouldn't replace the previous LTS version
>> as it hasn't reached end of life https://nodejs.org/en/about/releases/
>
> It will be end-of-life in two months.  More generally, I don't see the
End of life is 	2023-04-30
> appeal of packaging old versions, especially old versions that will
> soon be unsupported, when there are newer versions (16.X.Y) that will
> be supported for a relatively long time (two years).
>
> Also, a question for zamfofex: do the existing node packages still
> build, or are there (new) build failures after the patch?
>
> Greetings,
> Maxime.
>
> Attachments:
> * signature.asc

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

From: Maxime Devos <maximedevos <at> telenet.be>
To: "code <at> ceephax.com" <code <at> ceephax.com>, 53414 <at> debbugs.gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 13:38:02 +0100

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

code <at> ceephax.com schreef op vr 25-02-2022 om 11:24 [+0000]:
> It will be end-of-life in two months.  More generally, I don't see
> the
End of life is 	2023-04-30

I looked at the wrong version (v12 instead of v14), it's a year and two
months instead of two months.  Still, the latest LTS (v16) seems better
to me since it is newer and will be supported for longer.

Greetings,
Maxime.

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

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

From: Attila Lendvai <attila <at> lendvai.name>
To: "53414 <at> debbugs.gnu.org" <53414 <at> debbugs.gnu.org>
Subject: Re: [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 13:09:11 +0000

> Still, the latest LTS (v16) seems better to me since it is newer and will be
> supported for longer.

with packages like nodejs one often needs both older and newer versions in
parallel to also be able to build projects that haven't been ported to the new
nodejs.

note that this supersedes https://issues.guix.gnu.org/48396 (i don't know what
is the right way to record that fact in debbugs, besides this note).

--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Everything is interesting if you go into it *deeply* enough.”
	— Richard Feynman (1918–1988)

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

From: Maxime Devos <maximedevos <at> telenet.be>
To: Attila Lendvai <attila <at> lendvai.name>, "53414 <at> debbugs.gnu.org"
 <53414 <at> debbugs.gnu.org>
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 16:59:24 +0100

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

Attila Lendvai schreef op vr 25-02-2022 om 13:09 [+0000]:
> > Still, the latest LTS (v16) seems better to me since it is newer
> > and will be
> > supported for longer.
> 
> with packages like nodejs one often needs both older and newer
> versions in
> parallel to also be able to build projects that haven't been ported
> to the new
> nodejs.

Ignoring bootstrapping, this does not seem to be the case so far in
Guix -- the only results of "git grep -F \#\:node gnu" is

# 7 lines
gnu/packages/node.scm:     `(#:node ,node-bootstrap

so it seems that, except for bootstrapping, a single version of 'node'
suffices.

If it turns out that some packages still require v14, then we can
discuss that upstream, patch the package and/or introduce a 'node-14'
package variant, like we do with, say, autoconf, bcftools and gcc.

Actually 'gcc' does not point to the latest version, but to the
slightly older 10.3.0, but that's only due to core-updates concerns
and perhaps because upstream does -Werror too often.  And 'autoconf'
is not autoconf-2.71 because ‘this is the renaissance version, which is
not widelt supported yet’.  But AFAICT, there are no compatibility
concerns with v14->v16.

Greetings,
Maxime.

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

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

From: Pierre Langlois <pierre.langlois <at> gmx.com>
To: Maxime Devos <maximedevos <at> telenet.be>
Cc: "53414 <at> debbugs.gnu.org" <53414 <at> debbugs.gnu.org>,
 Attila Lendvai <attila <at> lendvai.name>, guix-patches <at> gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 16:31:12 +0000

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

Hi all,

Maxime Devos <maximedevos <at> telenet.be> writes:

> [[PGP Signed Part:Undecided]]
> Attila Lendvai schreef op vr 25-02-2022 om 13:09 [+0000]:
>> > Still, the latest LTS (v16) seems better to me since it is newer
>> > and will be
>> > supported for longer.
>> 
>> with packages like nodejs one often needs both older and newer
>> versions in
>> parallel to also be able to build projects that haven't been ported
>> to the new
>> nodejs.
>
> Ignoring bootstrapping, this does not seem to be the case so far in
> Guix -- the only results of "git grep -F \#\:node gnu" is
>
> # 7 lines
> gnu/packages/node.scm:     `(#:node ,node-bootstrap
>
> so it seems that, except for bootstrapping, a single version of 'node'
> suffices.

If I may shime in, I agree that it's best to have fewer versions of node
for Guix's own node packages, however for end-users I think it's a good
idea to provide multiple versions they can install.

I am not a web developper so if anybody knows better please correct me
:-), but I think it's common for a website projects to depend on a
specific supported LTS version of node.  For example, one time I
contributed to a project that recommended using a "node version manager"
script, https://github.com/nvm-sh/nvm, to easily switch between node
versions for different project.  This script seems pretty popular, but
it downloads official binaries :-/, Guix provides much better tools to
do this by default.

So I'm thinking it might make Guix more appealing to web developpers if
we provided multiple versions of node, only the LTS releases though I'd
say. For nodejs applications packaged in Guix though, I agree we don't
want multiple versions.

Thanks,
Pierre

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

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

From: Maxime Devos <maximedevos <at> telenet.be>
To: Pierre Langlois <pierre.langlois <at> gmx.com>
Cc: "53414 <at> debbugs.gnu.org" <53414 <at> debbugs.gnu.org>,
 Attila Lendvai <attila <at> lendvai.name>, guix-patches <at> gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 18:22:22 +0100

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

Pierre Langlois schreef op vr 25-02-2022 om 16:31 [+0000]:
> If I may shime in, I agree that it's best to have fewer versions of
> node
> for Guix's own node packages, however for end-users I think it's a
> good
> idea to provide multiple versions they can install.

I'm not opposed to including multiple LTS versions, as long as they
are supported upstream, there actual users of the old LTS versions
and there is some reason to use older versions (perhaps there are
a few incompatibilities?).

However, I would prefer the latest version to be standard version
(with variable name node-lts) so node packages in Guix use the latest
LTS by default.  Something like

(define-public node-lts
  (package
    (inherit node)
    (version "16.13.2")
    [...]))

;; Older LTS versions, still maintained upstream and used (see <...>).
;; There are some incompatibilities between [...], so allow users
;; to choose which node to use.
(define-public node-14
  (package
    (inherit node-lts)
    (version "14.[...]")
    [...]))

Greetings,
Maxime.

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

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

From: Ryan Sundberg <ryan <at> arctype.co>
To: guix-patches <at> gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Sun, 1 May 2022 23:10:13 -0700

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

Hello all, here is a revised version of zamfofex's patch that inherits
from node-14. I tried to trim as much fat out as possible in the
inherited node-(16-)lts, but some of the package arguments were
divergent in minor ways. I also bumped the version to 16.5.0 in the
meantime.

--
Sincerely,
Ryan Sundberg

On 2/25/22 9:22 AM, Maxime Devos wrote:
> Pierre Langlois schreef op vr 25-02-2022 om 16:31 [+0000]:
>> If I may shime in, I agree that it's best to have fewer versions of
>> node
>> for Guix's own node packages, however for end-users I think it's a
>> good
>> idea to provide multiple versions they can install.
> 
> I'm not opposed to including multiple LTS versions, as long as they
> are supported upstream, there actual users of the old LTS versions
> and there is some reason to use older versions (perhaps there are
> a few incompatibilities?).
> 
> However, I would prefer the latest version to be standard version
> (with variable name node-lts) so node packages in Guix use the latest
> LTS by default.  Something like
> 
> (define-public node-lts
>   (package
>     (inherit node)
>     (version "16.13.2")
>     [...]))
> 
> ;; Older LTS versions, still maintained upstream and used (see <...>).
> ;; There are some incompatibilities between [...], so allow users
> ;; to choose which node to use.
> (define-public node-14
>   (package
>     (inherit node-lts)
>     (version "14.[...]")
>     [...]))
> 
> Greetings,
> Maxime.

[0001-gnu-node-lts-Update-to-16.15.0.patch (text/x-patch, attachment)]

[OpenPGP_signature (application/pgp-signature, attachment)]

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

From: Pierre Langlois <pierre.langlois <at> gmx.com>
To: Ryan Sundberg <ryan <at> arctype.co>
Cc: 53414 <at> debbugs.gnu.org, guix-patches <at> gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Sun, 15 May 2022 14:45:16 +0100

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

Hi!

Ryan Sundberg via Guix-patches via <guix-patches <at> gnu.org> writes:

> [[PGP Signed Part:Undecided]]
> Hello all, here is a revised version of zamfofex's patch that inherits
> from node-14. I tried to trim as much fat out as possible in the
> inherited node-(16-)lts, but some of the package arguments were
> divergent in minor ways. I also bumped the version to 16.5.0 in the
> meantime.

The patch LGTM, however when testing it out I wasn't able to build node
packages, I get the following error for example:

--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix build node-string-decoder
...
starting phase `install'
npm info using npm <at> 8.5.5
npm info using node <at> v16.15.0
npm timing npm:load:whichnode Completed in 1ms
npm timing config:load:defaults Completed in 1ms
npm timing config:load:file:/gnu/store/4iqwfsbapa3lhhap1jyg0bry8d1373li-node-16.15.0/lib/node_modules/npm/npmrc Completed in 2ms
npm timing config:load:builtin Completed in 2ms
npm timing config:load:cli Completed in 3ms
npm timing config:load:env Completed in 0ms
npm timing config:load:project Completed in 1ms
npm timing config:load:file:/tmp/guix-build-node-string-decoder-1.3.0.drv-0/npm-home-0/.npmrc Completed in 2ms
npm timing config:load:user Completed in 2ms
npm timing config:load:file:/gnu/store/72cb549aap0inzc8d0v959w6z8qz964m-node-string-decoder-1.3.0/etc/npmrc Completed in 0ms
npm timing config:load:global Completed in 1ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:credentials Completed in 0ms
npm timing config:load:setEnvs Completed in 1ms
npm timing config:load Completed in 11ms
npm timing npm:load:configload Completed in 11ms
npm timing npm:load:setTitle Completed in 0ms
npm timing config:load:flatten Completed in 1ms
npm timing npm:load:display Completed in 5ms
npm timing npm:load:logFile Completed in 4ms
npm timing npm:load:timers Completed in 0ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load Completed in 21ms
npm timing arborist:ctor Completed in 1ms
npm timing idealTree:init Completed in 4ms
npm timing idealTree:userRequests Completed in 42ms
npm timing idealTree:#root Completed in 19ms
npm timing idealTree:node_modules/string_decoder Completed in 3ms
npm timing idealTree:node_modules/string_decoder/node_modules/safe-buffer Completed in 0ms
npm timing idealTree:buildDeps Completed in 24ms
npm timing idealTree:fixDepFlags Completed in 0ms
npm timing idealTree Completed in 73ms
npm timing reify:loadTrees Completed in 74ms
npm timing reify:diffTrees Completed in 1ms
npm timing reify:retireShallow Completed in 1ms
npm timing reify:createSparse Completed in 0ms
npm timing reify:trashOmits Completed in 0ms
npm timing reify:loadBundles Completed in 0ms
npm timing reify:audit Completed in 0ms
npm timing reifyNode:node_modules/string_decoder/node_modules/safe-buffer Completed in 8ms
npm timing reifyNode:node_modules/string_decoder Completed in 12ms
npm timing reify:unpack Completed in 13ms
npm timing reify:unretire Completed in 0ms
npm timing build:queue Completed in 1ms
npm timing build:deps Completed in 1ms
npm timing build:queue Completed in 0ms
npm timing build:links Completed in 1ms
npm timing build Completed in 2ms
npm timing reify:build Completed in 2ms
npm timing reify:trash Completed in 0ms
npm timing command:install Completed in 98ms
npm ERR! Cannot set properties of null (setting 'dev')
npm timing npm Completed in 279ms

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/guix-build-node-string-decoder-1.3.0.drv-0/npm-home-0/.npm/_logs/2022-05-15T13_47_30_141Z-debug-0.log
error: in phase 'install': uncaught exception:
%exception #<&invoke-error program: "/gnu/store/4iqwfsbapa3lhhap1jyg0bry8d1373li-node-16.15.0/bin/npm" arguments: ("--prefix" "/gnu/store/72cb549aap0inzc8d0v959w6z8qz964m-node-string-decoder-1.3.0" "--global" "--offline" "--loglevel" "info" "--production" "install" "../package.tgz") exit-status: 1 term-signal: #f stop-signal: #f>
phase `install' failed after 0.4 seconds
command "/gnu/store/4iqwfsbapa3lhhap1jyg0bry8d1373li-node-16.15.0/bin/npm" "--prefix" "/gnu/store/72cb549aap0inzc8d0v959w6z8qz964m-node-string-decoder-1.3.0" "--global" "--offline" "--loglevel" "info" "--production" "install" "../package.tgz" failed with status 1
builder for `/gnu/store/6a1vjam7gx0znrr8yngaw2lqld9868l0-node-string-decoder-1.3.0.drv' failed with exit code 1
build of /gnu/store/6a1vjam7gx0znrr8yngaw2lqld9868l0-node-string-decoder-1.3.0.drv failed
View build log at '/var/log/guix/drvs/6a/1vjam7gx0znrr8yngaw2lqld9868l0-node-string-decoder-1.3.0.drv.gz'.
guix build: error: build of `/gnu/store/6a1vjam7gx0znrr8yngaw2lqld9868l0-node-string-decoder-1.3.0.drv' failed
--8<---------------cut here---------------end--------------->8---

I'm a bit clueless as to what's happening, it could be a flavour of this
issue upstream: https://github.com/npm/cli/issues/3847

So hopefully this will be resolved with a new node release, in the
meantime, we could still package node 16 but not make it the default
node for the build-system, WDYT?  I'd suggest to keep the node-lts
pointing to the node-14 version.

Also, as an aside, I'm afraid the patch doesn't allow node to be
cross-compiled, but that's also currently broken on master so we could
fix that as a follow-up IMO.

Thanks for working on this!
Pierre

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

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

From: Ryan Sundberg <ryan <at> arctype.co>
To: Pierre Langlois <pierre.langlois <at> gmx.com>
Cc: 53414 <at> debbugs.gnu.org, guix-patches <at> gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Wed, 8 Jun 2022 23:39:06 -0700

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

Hi all, attached is a revised patch that keeps node-lts bound to node-14
and just adds the new node-16.

Thank you for the feedback Pierre, I agree we should not break any
packages by transitioning node-lts over without testing.

I also updated again to 16.15.1 from 16.15.0 here.

--Ryan Sundberg

[0001-gnu-node-16-Package-node.js-version-16.15.1.patch (text/x-patch, attachment)]

[OpenPGP_signature (application/pgp-signature, attachment)]

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

From: Maxime Devos <maximedevos <at> telenet.be>
To: Ryan Sundberg <ryan <at> arctype.co>, Pierre Langlois <pierre.langlois <at> gmx.com>
Cc: 53414 <at> debbugs.gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Thu, 09 Jun 2022 22:49:38 +0200

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

Ryan Sundberg via Guix-patches via schreef op wo 08-06-2022 om 23:39 [-
0700]:
> +                  #t))))

No need to return #t.

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

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

From: Maxime Devos <maximedevos <at> telenet.be>
To: Ryan Sundberg <ryan <at> arctype.co>, Pierre Langlois <pierre.langlois <at> gmx.com>
Cc: 53414 <at> debbugs.gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Thu, 09 Jun 2022 22:50:23 +0200

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

Ryan Sundberg via Guix-patches via schreef op wo 08-06-2022 om 23:39 [-
0700]:
> +       ((#:phases phases)
> +        `(modify-phases ,phases

Do #~(modify-phases #$phases ...) instead of quasiquote/unquote,
otherwise this will break when node-14 switches to G-exps.

Greetings,
Maxime.

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

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

From: Maxime Devos <maximedevos <at> telenet.be>
To: Ryan Sundberg <ryan <at> arctype.co>, Pierre Langlois <pierre.langlois <at> gmx.com>
Cc: 53414 <at> debbugs.gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Thu, 09 Jun 2022 22:53:43 +0200

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

Ryan Sundberg via Guix-patches via schreef op wo 08-06-2022 om 23:39 [-
0700]:
> +              (modules '((guix build utils)))
> +              (snippet
> +               `(begin
> +                  ;; Remove bundled software, where possible
> +                  (for-each delete-file-recursively
> +                            '("deps/cares"
> +                              "deps/icu-small"
> +                              "deps/nghttp2"
> +                              "deps/openssl"
> +                              "deps/zlib"))
> +                  (substitute* "Makefile"
> +                    ;; Remove references to bundled software.
> +                    (("deps/uv/uv.gyp") "")
> +                    (("deps/zlib/zlib.gyp") ""))
> +                  #t))))

This is identical to what node-14 has, so you can use inheritance to
simplify things:

  (origin
    (inherit (package-source node-14))
    (uri ...)
    (sha256 ...))

Also, could you verify that no new things have been bundled?

Greetings,
Maxime.

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

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

From: Maxime Devos <maximedevos <at> telenet.be>
To: Ryan Sundberg <ryan <at> arctype.co>, Pierre Langlois <pierre.langlois <at> gmx.com>
Cc: 53414 <at> debbugs.gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Thu, 09 Jun 2022 22:55:52 +0200

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

Ryan Sundberg via Guix-patches via schreef op wo 08-06-2022 om 23:39 [-
0700]:
> +                  (string-append "'" (assoc-ref inputs "bash")
> "/bin/sh'")))

Can be de-label-ified and simplified to (string-append "'" (search-
input-file inputs "bin/bash")).

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

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

From: Maxime Devos <maximedevos <at> telenet.be>
To: Ryan Sundberg <ryan <at> arctype.co>, Pierre Langlois <pierre.langlois <at> gmx.com>
Cc: 53414 <at> debbugs.gnu.org
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Thu, 09 Jun 2022 23:03:47 +0200

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

Ryan Sundberg via Guix-patches via schreef op wo 08-06-2022 om 23:39 [-
0700]:
> Hi all, attached is a revised patch that keeps node-lts bound to node-14
> and just adds the new node-16.
> 
> Thank you for the feedback Pierre, I agree we should not break any
> packages by transitioning node-lts over without testing.
> 
> I also updated again to 16.15.1 from 16.15.0 here.
> 
> --Ryan Sundberg

Debian's node package does some changes:

  * benchmark_without_alice.patch: removes something non-free
  * privacy_breach.patch: patch a html file to not point to something
    external
  * localhost-no-adrconfig.patch: a bug fix
  * test_ci.patch: flaky tests
  * skip-buffer-nan-internal-check.patch: remove broken test
  * falky-cpu-prof-riscv64.patch: likewise
  * flag_atomic.patch: ‘avoid surprises on ... and ppc*el’

Maybe some of them are needed on Guix as well?
(See https://packages.debian.org/sid/nodejs for a tarball with changes)

Greetings,
Maxime

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

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

From: Mekeor Melire <mekeor <at> posteo.de>
To: 53414 <at> debbugs.gnu.org
Cc: Maxime Devos <maximedevos <at> telenet.be>
Subject: Re: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Wed, 16 Nov 2022 23:23:00 +0000

2022-06-09 / 23:03 / maximedevos <at> telenet.be:

> Debian's node package does some changes:
>   * benchmark_without_alice.patch: removes something non-free

I'm not sure why Debian removes "Alice's Adventures in Wonderland"
because this work is in Public Domain. I think it's fine to keep it.

  https://github.com/nodejs/node/blob/main/benchmark/fixtures/alice.html

> Maybe some of them are needed on Guix as well?
> (See https://packages.debian.org/sid/nodejs for a tarball with changes)

Message #73 received at 53414-submitter <at> debbugs.gnu.org (full text, mbox):

From: Steve George <steve <at> futurile.net>
To: control <at> debbugs.gnu.org
Cc: 53414-submitter <at> debbugs.gnu.org
Subject: closing 53414
Date: Fri, 21 Feb 2025 11:14:19 +0000

close 53414 
quit

# Hi - we're up to 22.12.0 these days, so I think we can close this. If that's an error please re-open. Thanks!

Previous Next

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