This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
Missing shasum for arm-pi binary at http://nodejs.org/dist/v0.10.15/ #6338
Comments
|
Calling @TooTallNate. |
|
See #5460 for an explanation. |
|
Indeed, since these are delivered separately from the standard release process, we would need a separate set of shasums with their own signatures. @TooTallNate if you wanna do the pgp/gpg thing that would be great, or we can work out a procedure where you send me the tarballs and I sign them and put them up |
mdxp
pushed a commit
to mdxp/nodejs-cookbook
that referenced
this issue
Mar 4, 2014
Installing from a binary was failing on a Raspberry Pi due to a null string error. I added the shasum to the attributes/default.rb file. However, I used the shasum that I calculated locally. This is wrong. I tried to go to http://nodejs.org/dist/v0.10.15/ and get the shasum posted there from the gpg or asc file, however none of those checksum files, include the necessary checksum for the "arm-pi" flavor of NodeJS. In the absence of an official shasum, can someone find out how to get the tarball over https and confirm the shasum above before merging this pull request? I pulled the tarball over http and therefore my shasum should be treated as suspect until independently verified. In the meantime, I filed an issue over in the joyent/node repo: nodejs/node-v0.x-archive#6338
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am trying to verify the arm-pi distribution of
0.10.15at http://nodejs.org/dist/v0.10.15/ , but the shasum files do not contain a hash fornode-v0.10.15-linux-arm-pi.tar.gz. Can the person responsible for building it please update those files or at least make sure the shasum for arm-pi is included in future versions?(P.S. Is Github issues the right place to file this? I reckon some sort of check could be added to the build and bless scripts to make sure that every build at
nodejs.org/dist/has a shasum)related: mdxp/nodejs-cookbook#62
The text was updated successfully, but these errors were encountered: