From: jlicht@fsfe.org
To: 75384@debbugs.gnu.org
Cc: Jelle Licht <jlicht@fsfe.org>, dthompson2@worcester.edu
Subject: [bug#75384] [PATCH 0/4] Bump node-lts to 22.12.0
Date: Sun, 5 Jan 2025 18:48:56 +0100 [thread overview]
Message-ID: <cover.1736092552.git.jlicht@fsfe.org> (raw)
From: Jelle Licht <jlicht@fsfe.org>
Hi all, this series bumps node-lts to version 22.12.0.
I had to reintroduce a c-ares package variant specific to node-lts, as well as
disable some tests that did not work in the build container for one reason or
another.
To keep the llhttp-bootstrap dance as short as possible, I've adapted a
so-called ponyfill[0] for Object.fromEntries so we can directly build llhttp
9.2.1 using our node-bootstrap package.
[0] https://github.com/feross/fromentries/tree/master#what-is-a-ponyfill
Jelle Licht (4):
gnu: Add c-ares-for-node-lts.
gnu: libuv-for-node-lts: Update to 1.49.1.
gnu: llhttp-bootstrap: Update to 9.2.1.
gnu: node-lts: Update to 22.12.0.
gnu/local.mk | 1 +
gnu/packages/adns.scm | 15 ++++++
gnu/packages/libevent.scm | 12 +----
gnu/packages/node.scm | 23 ++++++----
.../llhttp-ponyfill-object-fromentries.patch | 46 +++++++++++++++++++
5 files changed, 77 insertions(+), 20 deletions(-)
create mode 100644 gnu/packages/patches/llhttp-ponyfill-object-fromentries.patch
base-commit: 67a535351f8678969e412e8dba9197a883b524d0
--
2.47.1
next reply other threads:[~2025-01-05 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 17:48 jlicht [this message]
2025-01-05 17:57 ` [bug#75384] [PATCH 1/4] gnu: Add c-ares-for-node-lts jlicht
2025-01-05 17:57 ` [bug#75384] [PATCH 2/4] gnu: libuv-for-node-lts: Update to 1.49.1 jlicht
2025-01-05 17:57 ` [bug#75384] [PATCH 3/4] gnu: llhttp-bootstrap: Update to 9.2.1 jlicht
2025-01-05 17:57 ` [bug#75384] [PATCH 4/4] gnu: node-lts: Update to 22.12.0 jlicht
2025-01-08 16:36 ` [bug#75384] [PATCH 0/4] Bump node-lts " Thompson, David
2025-01-24 9:15 ` Jelle Licht
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=cover.1736092552.git.jlicht@fsfe.org \
--to=jlicht@fsfe.org \
--cc=75384@debbugs.gnu.org \
--cc=dthompson2@worcester.edu \
/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.