($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: archana.polampalli@windriver.com
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe][meta-oe][PATCH 1/1] nodejs: upgrade 20.11.1 -> 20.12.2
Date: Fri, 3 May 2024 11:50:19 +0200	[thread overview]
Message-ID: <CA+chaQfPhbJgPw+iLZkC67Ld-89TckhWHj6koYsSer8xXtRxUQ@mail.gmail.com> (raw)
In-Reply-To: <20240425082519.2888002-1-archana.polampalli@windriver.com>

Hi,

since this update I'm seeing couple of npmsw:// recipes failing with
ENOTCACHED for various dependencies, e.g.:

npm ERR! code ENOTCACHED
npm ERR! request to https://registry.npmjs.org/documentation failed:
cache mode is 'only-if-cached' but no cached response is available.
--
npm ERR! code ENOTCACHED
npm ERR! request to https://registry.npmjs.org/@babel%2feslint-plugin
failed: cache mode is 'only-if-cached' but no cached response is
available.

reverting npm upgrade from 10.3.0 to 10.5.0 from:
https://github.com/nodejs/node/commit/208dd887a5
https://github.com/nodejs/node/pull/51913
seems to fix this issue. Refreshing the shrinkwrap with 10.5.0 npm
produces identical shrinkwrap.

Is anyone else seeing this issue?

Cheers,


On Thu, Apr 25, 2024 at 10:25 AM Polampalli, Archana via
lists.openembedded.org
<archana.polampalli=windriver.com@lists.openembedded.org> wrote:
>
> From: Archana Polampalli <archana.polampalli@windriver.com>
>
> License-Update:
>     Copyright year updated
>     zlib version updated
>     GN files License update
>
> https://github.com/nodejs/node/commit/b5bc597871ca701bab750c46d31ed626decd7f89
> https://github.com/nodejs/node/commit/c8233912e9fd7464898b549d6762130722bf0bf4
>
> Changelog:
> https://github.com/nodejs/node/releases/tag/v20.12.2
> https://github.com/nodejs/node/releases/tag/v20.12.1
> https://github.com/nodejs/node/releases/tag/v20.12.0
>
> Signed-off-by: Archana Polampalli <archana.polampalli@windriver.com>
> ---
>  .../oe-npm-cache                                              | 0
>  ...-cache-native_20.11.bb => nodejs-oe-cache-native_20.12.bb} | 0
>  .../nodejs/{nodejs_20.11.1.bb => nodejs_20.12.2.bb}           | 4 ++--
>  3 files changed, 2 insertions(+), 2 deletions(-)
>  rename meta-oe/recipes-devtools/nodejs/{nodejs-oe-cache-20.11 => nodejs-oe-cache-20.12}/oe-npm-cache (100%)
>  rename meta-oe/recipes-devtools/nodejs/{nodejs-oe-cache-native_20.11.bb => nodejs-oe-cache-native_20.12.bb} (100%)
>  rename meta-oe/recipes-devtools/nodejs/{nodejs_20.11.1.bb => nodejs_20.12.2.bb} (97%)
>
> diff --git a/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-20.11/oe-npm-cache b/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-20.12/oe-npm-cache
> similarity index 100%
> rename from meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-20.11/oe-npm-cache
> rename to meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-20.12/oe-npm-cache
> diff --git a/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_20.11.bb b/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_20.12.bb
> similarity index 100%
> rename from meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_20.11.bb
> rename to meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_20.12.bb
> diff --git a/meta-oe/recipes-devtools/nodejs/nodejs_20.11.1.bb b/meta-oe/recipes-devtools/nodejs/nodejs_20.12.2.bb
> similarity index 97%
> rename from meta-oe/recipes-devtools/nodejs/nodejs_20.11.1.bb
> rename to meta-oe/recipes-devtools/nodejs/nodejs_20.12.2.bb
> index 9a61cfcf7..d86c38f2f 100644
> --- a/meta-oe/recipes-devtools/nodejs/nodejs_20.11.1.bb
> +++ b/meta-oe/recipes-devtools/nodejs/nodejs_20.12.2.bb
> @@ -1,7 +1,7 @@
>  DESCRIPTION = "nodeJS Evented I/O for V8 JavaScript"
>  HOMEPAGE = "http://nodejs.org"
>  LICENSE = "MIT & ISC & BSD-2-Clause & BSD-3-Clause & Artistic-2.0 & Apache-2.0"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=78ad16dab3c1d15d4878c81770be0be7"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=9a7fcce64128730251dbc58aa41b4674"
>
>  CVE_PRODUCT = "nodejs node.js"
>
> @@ -36,7 +36,7 @@ SRC_URI:append:toolchain-clang:x86 = " \
>  SRC_URI:append:toolchain-clang:powerpc64le = " \
>             file://0001-ppc64-Do-not-use-mminimal-toc-with-clang.patch \
>             "
> -SRC_URI[sha256sum] = "77813edbf3f7f16d2d35d3353443dee4e61d5ee84d9e3138c7538a3c0ca5209e"
> +SRC_URI[sha256sum] = "d7cbcc5fbfb31e9001f3f0150bbeda59abe5dd7137aaa6273958cd59ce35ced7"
>
>  S = "${WORKDIR}/node-v${PV}"
>
> --
> 2.40.0
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#110150): https://lists.openembedded.org/g/openembedded-devel/message/110150
> Mute This Topic: https://lists.openembedded.org/mt/105726620/3617156
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [martin.jansa@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


      reply	other threads:[~2024-05-03  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25  8:25 [oe][meta-oe][PATCH 1/1] nodejs: upgrade 20.11.1 -> 20.12.2 archana.polampalli
2024-05-03  9:50 ` Martin Jansa [this message]

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=CA+chaQfPhbJgPw+iLZkC67Ld-89TckhWHj6koYsSer8xXtRxUQ@mail.gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=archana.polampalli@windriver.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).