no ARMv6 download of Nodejs 8.x available, 404 link

[jimmont]

• https://nodejs.org/en/download/current/:
• ALL:
• ALL:

see heading: "Linux Binaries (ARM)" with link "ARMv6" with href "https://nodejs.org/dist/v8.6.0/node-v8.6.0-linux-armv6l.tar.xz" which is a 404 error and browsing to "https://nodejs.org/dist/v8.6.0/" has no ARMv6 compatible download.

[refack]

@jimmont I think I found them nodejs/build#897 for some reason they were named ARM7, and it's actually the ARM7 binaries that are missing.

/cc @nodejs/build @nodejs/release

[jimmont]

@refack unfortunately the ARM7 binary you mentioned from https://nodejs.org/dist/v8.6.0/node-v8.6.0-linux-armv7l.tar.xz segfaults on my ARM6 machine so I don't think it's an option.

[jimmont]

Reverting to Nodejs 8.4 per what appears to be the best option based on descriptions of the most recent 2 security issues (as of today).
https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/
https://groups.google.com/forum/#!forum/nodejs-sec

[refack]

So it's not a simple misnaming, shame.
You might want to checkout nodesource's repository https://github.com/nodesource/distributions, they build binaries to various linux distributions and support ARM6 & ARM7

[jimmont]

Unfortunately Nodejs 8.x and 7.x are not supported for ARM6 on nodesource. Appreciate the tip @refack, might be time to retire the rpi I've been using.

[joaocgreis]

This happened because all of our ARMv6 infra is down. ARMv6 is still supported and the binary will probably be released as soon as we're able to get the machines back online (cc @rvagg).

The ARMv7 issue is a different one, ref nodejs/build#829.

[mhdawson]

I guess I need to find time to get the backup Raspberry PI 1 (ARM v6) connected to the CI. However, that won't like be until at least after Node Interactive.

[jimmont]

@mhdawson Michael is it possible to please update the page to reflect the status for these downloads accurately? If there's a change in support or outage (indicated above) it would be helpful to have that information on the website so that we can plan accordingly. Thank you.

[refack]

ping @jasnell who cut the release (No ARM6 and ARM7 are corrupt)

[johnwebbcole]

I appears that node source isn't an option for armv6l versions of v8.x

## Installing the NodeSource Node.js v8.x repo...


## You appear to be running on ARMv6 hardware. Unfortunately this is not currently supported by the NodeSource Linux distributions. Please use the 'linux-armv6l' binary tarballs available directly from nodejs.org for Node.js v4 and later.

Any word on the armv6 builds?

Thx!

[mhdawson]

The arm machine seems to be online but fails with this:

/home/iojs/build/ws/out/Release/.deps//home/iojs/build/ws/out/Release/obj.target/v8_base/deps/v8/src/ic/arm/handler-compiler-arm.o.d.raw   -c -o /home/iojs/build/ws/out/Release/obj.target/v8_base/deps/v8/src/ic/arm/handler-compiler-arm.o ../deps/v8/src/ic/arm/handler-compiler-arm.cc
FATAL: command execution failed
java.nio.channels.ClosedChannelException
	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208)
	at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)
	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
	at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFil

@rvagg is it possible that some cleanup is needed on the release machine ?

[bertlea]

Hi Guys, the same issue seems happening to v8.9.1 now. No armv6l distribution in the download list. the v8.9.0 still got it and also v9.2.0 got it too.

[mhdawson]

We do have issues with our arm6 builds in that they take a long time to compile due to the low machine resources and often timeout or have some other issue during the long run.

@gibfahn I've added a new arm6 only build that we can run to rebuild just the arm6 binaries in case of failure. If we run that for 8.9.1 with the right parameters is that enough or do we need additional steps to sign/validate the hashes ?