[ERROR] Node.js v22 out of date for armhf

[passibe15]

Describe your bug The latest versions of Node.js v22 for armhf are not available. The newest version available is 22.15.0, while there should be 22.17.1 already.

Distribution Information:

• OS: Raspbian
• Version: 12/bookworm
• Architecture: armhf/armv7l

Node Version:

• Node: Node.js v22

To Reproduce

1. Install regularly, i.e. with curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash - and sudo apt-get install -y nodejs
2. Check node -v, it prints: v22.15.0
3. Check apt-cache madison nodejs, it prints:

   nodejs | 22.15.0-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
   nodejs | 22.14.0-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
   nodejs | 22.13.1-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
   nodejs | 22.13.0-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
   nodejs | 22.12.0-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
   nodejs | 22.11.0-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
   nodejs | 22.10.0-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main armhf Packages
   […]
   

Expected behavior I expect the latest versions to be available for armhf, just like they are for e.g. amd64:

nodejs | 22.17.1-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
nodejs | 22.17.0-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
nodejs | 22.16.0-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
nodejs | 22.15.1-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
nodejs | 22.15.0-1nodesource1 | https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
[…]

[Grothesk242]

Same is true for nodejs@20

[KEGustafsson]

And setup_24.x or setup_current.x for arch armv7l installs v18.

[Grothesk242]

Looking into the installer scripts you can see that archictures other than 'amd64 and 'arm64' are not supported anymore. I just can't find any official announcement for this.

[passibe15]

Where do you see this? In setup_22.x on line 79 it (clearly) says: Only amd64, arm64, and armhf are supported. So armhf is still supposed to be supported, at least for v22.

---

tbh it's very concerning issues like this one, and especially issues like https://github.com/nodesource/distributions/issues/1882 and https://github.com/nodesource/distributions/issues/1865 have been open for over three months now with no official response/action (https://github.com/nodesource/distributions/issues/1865 has been open even longer, since late May).

This doesn't really fit a company who's mission supposedly is to

empower organizations of all sizes to successfully adopt and integrate Node.js by providing products and services that enable teams to build, manage, and analyze mission-critical applications.

I wouldn't want to base any "mission-critical applications" on services provided by someone who can't even be bothered to update their GPG keys.

[Grothesk242]

Where do you see this?

In the installerscript for nodejs@24 armhf is excluded. And nodejs 22.15.x is the last version from the 22 tree that is available via the repo.

[passibe15]

In the installerscript for nodejs@24 armhf is excluded.

Cool okay, but this issue is about v22.

And nodejs 22.15.x is the last version from the 22 tree that is available via the repo.

No, not for other architectures. This is precisely the issue, that it is outdated specifically for armhf. Just read the original issue, please.

[Grothesk242]

I consider armhf as obsolete. I think nobody will provide anything newer than 22.15.0. Time to say goodbye to current nodejs on armhf.

[passibe15]

I don't care what you consider as obsolete.

I think nobody will provide anything newer than 22.15.0.

This is just wrong. Official builds for armhf still exist, even for v22.21.x (they label it as ARMv7).

And I expect nodesource to provide these builds in their repo, if a) they themselves state that it is a compatible architecture and b) they provide the newest version of v22 for all other architectures as well.

I suspect this is just some bug somewhere in the pipeline. This has happened before (see e.g. https://github.com/nodesource/distributions/issues/1840#issuecomment-2523812727) and now, for whatever reason, they are just too lazy to fix it. It's not like they sat down and thought "hmm let's no longer provide this even though official builds are still released".

[Grothesk242]

I don't care what you consider as obsolete.

And I don't care what you expect. Fact is, that the nodesource-Repositories are a mess in the last months. Releases pop up in the wrong repos, releases disappear, keys are outdated, [email protected] is not published.

I think that armhf has been silently abandoned by nodesource. And I don't expect that it get's build for an architecture that will not see a nodejs@24 release.

[FabianFrank]

And I don't care what you expect.

People reasonably expect the LTS lifecycle to be followed by a project claiming to provide nodejs binaries for current versions. This means armv7 builds until 22.x falls out of LTS in 2027 and would give armv7 users a lot of time to upgrade. However, nodesource somehow gave up on 22.x (for no reason?) and hung everyone on armv7 out to dry mid-cycle. IMHO the frustration around this is deserved.

My guess is they want you on their commercial distribution (armhv n packages are available for the 22.x versions in question as well as 24.x) so for them abandoning 22.x makes business sense. For 24.x this seems fair, it is no longer officially supported after all, but artificially accelerating that drop in support feels bad.

All complaining is no use though, you have to decide to either pay, accept to be on a poorly maintained nodejs binary source or switch to a different binary source. I'll do the latter.

[passibe15]

decide to either pay

Yeah lol as if I'd be willing to pay people who can't even be bothered to fix simple issues. All of this, especially stuff like https://github.com/nodesource/distributions/issues/1865, are just bad PR for them. Not sure what their business strategy is here.