From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Kyle Discher <discher.kyle@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/nodejs: bump to 16.15.0
Date: Thu, 12 May 2022 22:17:29 +0200 [thread overview]
Message-ID: <20220512201729.GG1597494@scaer> (raw)
In-Reply-To: <CAPa6QFar5zopEzDpJvz_aO9Q-yK20EZrT=aA+gb=bMrxcELNYg@mail.gmail.com>
Kyle, All,
On 2022-05-11 08:03 -0700, Kyle Discher spake thusly:
> Oops, I forgot:
> Signed-off-by: Kyle Discher < [1]discher.kyle@gmail.com>
Thanks, I've added that when applying to master.
Regards,
Yann E. MORIN.
> On Mon, May 9, 2022, 10:16 AM Kyle Discher < [2]discher.kyle@gmail.com> wrote:
>
> ---
> package/nodejs/nodejs.hash | 4 ++--
> package/nodejs/ [3]nodejs.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/nodejs/nodejs.hash b/package/nodejs/nodejs.hash
> index 6365ef852b..998229341e 100644
> --- a/package/nodejs/nodejs.hash
> +++ b/package/nodejs/nodejs.hash
> @@ -1,5 +1,5 @@
> -# From [4]https://nodejs.org/dist/v14.18.3/SHASUMS256.txt
> -sha256 783ac443cd343dd6c68d2abcf7e59e7b978a6a428f6a6025f9b84918b769d608 node-v14.18.3.tar.xz
> +# From [5]https://nodejs.org/dist/v16.15.0/SHASUMS256.txt
> +sha256 a0f812efc43f78321eca08957960a48f5e6bf97004d5058c8dd3b03c646ea4f7 node-v16.15.0.tar.xz
>
> # Hash for license file
> sha256 b3a67885b5a6ac35e8bbe8190509e41b79b0d9a2e3fbd47186f2ac4727f63be5 LICENSE
> diff --git a/package/nodejs/ [6]nodejs.mk b/package/nodejs/ [7]nodejs.mk
> index 4fe34e0aad..6dcaf34aa4 100644
> --- a/package/nodejs/ [8]nodejs.mk
> +++ b/package/nodejs/ [9]nodejs.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -NODEJS_VERSION = 14.18.3
> +NODEJS_VERSION = 16.15.0
> NODEJS_SOURCE = node-v$(NODEJS_VERSION).tar.xz
> NODEJS_SITE = [10]http://nodejs.org/dist/v$(NODEJS_VERSION)
> NODEJS_DEPENDENCIES = host-qemu host-pkgconf host-python3 host-nodejs c-ares \
> --
> 2.36.1
>
> Links:
> 1. mailto:discher.kyle@gmail.com
> 2. mailto:discher.kyle@gmail.com
> 3. http://nodejs.mk
> 4. https://nodejs.org/dist/v14.18.3/SHASUMS256.txt
> 5. https://nodejs.org/dist/v16.15.0/SHASUMS256.txt
> 6. http://nodejs.mk
> 7. http://nodejs.mk
> 8. http://nodejs.mk
> 9. http://nodejs.mk
> 10. http://nodejs.org/dist/v$(NODEJS_VERSION)
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-12 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220509171602.18228-1-discher.kyle@gmail.com>
2022-05-11 15:03 ` [Buildroot] [PATCH] package/nodejs: bump to 16.15.0 Kyle Discher
2022-05-12 20:17 ` Yann E. MORIN [this message]
2022-05-09 17:22 Kyle Discher
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=20220512201729.GG1597494@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=discher.kyle@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox