** Also affects: chromium (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: chromium (Ubuntu)
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
** Tags added: noble riscv
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2118978
Title:
Request for node 22
Status in chromium-browser package in Ubuntu:
Triaged
Status in nodejs package in Ubuntu:
New
Bug description:
Chromium fails to build[1] with
--->
:: AssertionError [ERR_ASSERTION]: Failed NodeJS version check: Expected
version 'v22.11.0', but found 'v18.19.1'. Did you run 'gclient sync'? If the
problem persists try running 'gclient sync -f' instead, or deleting
third_party/node/{linux,win,mac} folders and trying again.
:: at main
(file:///build/chromium/parts/chromium/build/third_party/node/check_version.js:37:10)
{
:: generatedMessage: false,
:: code: 'ERR_ASSERTION',
:: actual: 'v22.11.0',
:: expected: 'v18.19.1',
<---
How feasible is updating Node to 22 and then backporting it to 24.04?
Up to now we've been pulling the updated Node at build-time but Node
they do not publish binaries for Risc-V.
[1]
https://launchpadlibrarian.net/807881851/buildlog_snap_ubuntu_noble_arm64_chr-
dev-risc_BUILDING.txt.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2118978/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
