From: "code@ceephax.com" <code@ceephax.com>
To: "Maxime Devos" <maximedevos@telenet.be>, 53414@debbugs.gnu.org
Subject: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 11:24:45 +0000 [thread overview]
Message-ID: <4ce7393f-d9fe-4cf2-af4c-de154f977be9@www.fastmail.com> (raw)
In-Reply-To: <5f1f12681a242ac300d63edbf3ab28153440c409.camel@telenet.be>
On Fri, 25 Feb 2022, at 11:07, Maxime Devos wrote:
> code@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
next prev parent reply other threads:[~2022-02-25 11:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 15:11 [bug#53414] [PATCH] update Node LTS to 16.13.2 zamfofex
2022-02-23 13:13 ` code
2022-02-25 11:07 ` Maxime Devos
2022-02-25 11:24 ` code [this message]
2022-02-25 12:38 ` Maxime Devos
2022-02-25 13:09 ` Attila Lendvai
2022-02-25 15:59 ` Maxime Devos
2022-02-25 16:31 ` Pierre Langlois
2022-02-25 17:22 ` Maxime Devos
2022-05-02 6:10 ` Ryan Sundberg via Guix-patches via
2022-05-15 13:45 ` Pierre Langlois
2022-06-09 6:39 ` Ryan Sundberg via Guix-patches via
2022-06-09 20:49 ` Maxime Devos
2022-06-09 20:50 ` Maxime Devos
2022-06-09 20:53 ` Maxime Devos
2022-06-09 20:55 ` Maxime Devos
2022-06-09 21:03 ` Maxime Devos
2022-11-16 23:23 ` Mekeor Melire
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=4ce7393f-d9fe-4cf2-af4c-de154f977be9@www.fastmail.com \
--to=code@ceephax.com \
--cc=53414@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.