Re: [meta-oe][kirkstone][PATCH 1/1] Nodejs - Upgrade to 16.18.1

Martin Jansa

On Sat, Nov 26, 2022 at 5:05 PM akuster808 <akuster808@...> wrote:

On 11/24/22 2:18 PM, Martin Jansa wrote:
> On Thu, Nov 24, 2022 at 7:06 PM Randy MacLeod
> <randy.macleod@...> wrote:
>     Add Armin to ensure he seems this once he recovers from US
>     Thanksgiving indulgences.
>     On 2022-11-24 12:05, Martin Jansa wrote:
>>     I see this is now queued in kirkstone-next
>>     <;!!AjveYdw8EvQ!bcx80wmigop8Eoea7TohEOVlX1wPfDp0MAiO-8lZQDzv5nw5ai-FPfVsVaCxBstk-GtvN-eKnWtaUipHYjAMDDlyDWE$>
>>     I see bunch of recipes failing since this upgrade landed in
>>     master, mostly due to npm dependency resolution being more strict
>>     now and builds failing with
>>     npm ERR! code ERESOLVE
>>     npm ERR! ERESOLVE could not resolve
>>     ...
>>     npm ERR! Fix the upstream dependency conflict, or retry
>>     npm ERR! this command with --force, or --legacy-peer-deps
>>     npm ERR! to accept an incorrect (and potentially broken)
>>     dependency resolution.
>>     Can we please delay backporting to kirkstone and langdale a bit more?
>     Seconded!

Noted. will remove from kirkstone-next

I've tested my work arounds for both kinds of build failures I've mentioned here and it seems to work fine.

Nobody else reported seeing similar failures in this thread, so it might be less wide spread than what I've seen in our internal LGE layers (or other people aren't testing their builds against master often enough, which is their problem and shouldn't block this).

I'm no longer against getting this merged in langdale and kirkstone.

Join { to automatically receive all group messages.