From: Nisha Parrakat <nishaparrakat@gmail.com>
To: openembedded-devel@lists.openembedded.org, raj.khem@gmail.com
Cc: nishaparrakat@gmail.com
Subject: [meta-oe][dunfell][PATCH 2/2] nodejs: upgrade to 12.22.2
Date: Thu, 13 Jan 2022 09:13:01 +0100 [thread overview]
Message-ID: <20220113081301.26006-2-nishaparrakat@gmail.com> (raw)
In-Reply-To: <20220113081301.26006-1-nishaparrakat@gmail.com>
upgrading to next maintainence LTS version
Signed-off-by: Nisha Parrakat <nishaparrakat@gmail.com>
---
.../nodejs/{nodejs_12.21.0.bb => nodejs_12.22.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-devtools/nodejs/{nodejs_12.21.0.bb => nodejs_12.22.2.bb} (98%)
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs_12.21.0.bb b/meta-oe/recipes-devtools/nodejs/nodejs_12.22.2.bb
similarity index 98%
rename from meta-oe/recipes-devtools/nodejs/nodejs_12.21.0.bb
rename to meta-oe/recipes-devtools/nodejs/nodejs_12.22.2.bb
index 22191a157..8d533199b 100644
--- a/meta-oe/recipes-devtools/nodejs/nodejs_12.21.0.bb
+++ b/meta-oe/recipes-devtools/nodejs/nodejs_12.22.2.bb
@@ -26,7 +26,7 @@ SRC_URI = "http://nodejs.org/dist/v${PV}/node-v${PV}.tar.xz \
SRC_URI_append_class-target = " \
file://0002-Using-native-binaries.patch \
"
-SRC_URI[sha256sum] = "052f37ace6f569b513b5a1154b2a45d3c4d8b07d7d7c807b79f1566db61e979d"
+SRC_URI[sha256sum] = "7fd805571df106f086f4c45e131efed98bfd62628d9dec96bd62f8c11b0c48dc"
S = "${WORKDIR}/node-v${PV}"
--
2.17.1
next prev parent reply other threads:[~2022-01-13 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 8:13 [meta-oe][dunfell][PATCH 1/2] nodejs_12.21.0.bb: only handle npm if configured Nisha Parrakat
2022-01-13 8:13 ` Nisha Parrakat [this message]
2022-04-05 13:56 ` [meta-oe][dunfell][PATCH 2/2] nodejs: upgrade to 12.22.2 Ranjitsinh Rathod
2022-01-14 13:25 ` [oe] [meta-oe][dunfell][PATCH 1/2] nodejs_12.21.0.bb: only handle npm if configured Peter Kjellerstedt
2022-01-14 17:50 ` Martin Jansa
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=20220113081301.26006-2-nishaparrakat@gmail.com \
--to=nishaparrakat@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@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 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.