[ ---- ] Using a compatible nodejs version for all pi images
[ -- ] Removing previous nodejs installation from /usr/bin/node
[ ---- ] Removing Node v8.17.0 arm_version: 6
...
dpkg: error: cannot access archive '/volumio/customNode/nodejs_*-1unofficial_armv6l.deb': No such file or directory
[ error ] Imagebuilder script failed!!
[ -- ] Cleaning up image_tmp mounts
[ -- ] Unmounting chroot temporary devices at /mnt/volumio/rootfs
[ .. ] Cleaning loop device /dev/loop3 [ /dev/loop3: [2049]:9204885521 (/data/mevolumio/forks/Build/Volumio-buster-2021-01-10-raspberry.img) ]
[ .. ] Deleting image file
build.sh seems not to have populated /volumio/customNode.
The code in build.sh uses the variables USE_NODE_ARMV6 and the first element of the NODE_VERSION variables to decide if it's going to do that.
The version is 8.17.0 so the last criterion matches. I set DEVICE to raspberry so the first criterion matchies,
But USE_NODE_ARMV6 is a bit of a puzzle.
It gets defaulted to yes in build.sh if it is not set, but it seems to also be defaulted to yes in recipes/devices/raspberry.sh.
I notice it uses NODE_VERSION directly there, so the two decisions are potentially inconsistent with each other.
After a bit of inspection it seems that one has to manually download the relevant .deb and save it in a local directory.
Questions:
why doesn't the script do this? Lots of other custom .debs get downloaded in this way.
I was wanting to build an image for rpi4, which I understand uses an armv8 processor. But if I try to run
./build.sh -d raspberry -b armv8 -v buster
raspberry.shoverrides that, unconditionally. Theres a note about 'refactoring' the script, can someone expand on what that means?
xipmix
commented
3 years ago
I tried this
and got a fair way but it falls over here
build.sh seems not to have populated /volumio/customNode. The code in build.sh uses the variables USE_NODE_ARMV6 and the first element of the NODE_VERSION variables to decide if it's going to do that. The version is 8.17.0 so the last criterion matches. I set DEVICE to raspberry so the first criterion matchies, But USE_NODE_ARMV6 is a bit of a puzzle.
It gets defaulted to yes in build.sh if it is not set, but it seems to also be defaulted to yes in recipes/devices/raspberry.sh. I notice it uses NODE_VERSION directly there, so the two decisions are potentially inconsistent with each other.
After a bit of inspection it seems that one has to manually download the relevant .deb and save it in a local directory. Questions:
raspberry.shoverrides that, unconditionally. Theres a note about 'refactoring' the script, can someone expand on what that means?