Request for node 22
Bug #2118978 reported by
Nathan Teodosio
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| chromium-browser (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
| nodejs (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
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/
:: at main (file:/
:: 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.
| no longer affects: | chromium (Ubuntu) |
| Changed in chromium-browser (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: noble riscv |
Revision history for this message
| Simon Chopin (schopin) wrote | #1 |
Revision history for this message
| Heinrich Schuchardt (xypron) wrote | #2 |
Revision history for this message
| Heinrich Schuchardt (xypron) wrote | #3 |
Revision history for this message
| Heinrich Schuchardt (xypron) wrote | #4 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in nodejs (Ubuntu): | |
| status: | New → Confirmed |
To post a comment you must log in.
Disclaimer: absolutely not volunteering to do the work.
The backport would need to be done as a separate package, as I'm guessing Node 18 to 22 comes with a fair share of breakage. We have had similar approaches for other packages needed by browsers, e.g. cmake-mozilla in focal.