#35438 closed defect (bug) (wontfix)
Cannot download linux-arm-11_binding.node
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Build/Test Tools | Keywords: | |
| Focuses: | Cc: |
Description
After running:
git clone git://develop.git.wordpress.org/ develop cd develop npm install
I get this error:
Cannot download "https://github.com/sass/node-sass/releases/download/v3.4.2/linux-arm-11_binding.node":
HTTP error 404
Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.
export HTTP_PROXY=http://example.com:1234
or configure npm proxy via
npm config set proxy http://example.com:8080
To verify it wasn't a temporary glitch, I manually tried going to https://github.com/sass/node-sass/releases/download/v3.4.2/linux-arm-11_binding.node and got a 404.
Change History (5)
#1
@
10 years ago
- Milestone Awaiting Review deleted
- Resolution set to wontfix
- Status changed from new to closed
#3
@
10 years ago
Thanks for the info @dd32. The only packages that don't have armhf binaries seem to be phantomjs and node-sass. Are these must-have packages? If not, then perhaps I could forge ahead and simply wait for a build to become available upstream. If they are must-have, I might think about buying an Intel processor.
#4
@
10 years ago
Neither package is a must-have, however I'm not sure how our build tools will work with node-sass missing.
PhantomJS is only used for a few unit tests, node-sass is used for compiling the few sass stylesheets we have (The Colour Schemes).
node-sass has instructions on how to build a binary for your platform here: https://github.com/sass/node-sass#rebuilding-binaries
Unfortunately there doesn't appear to be a node-sass build available for the linux arm platform at this time.
It's a shame that this means the build tools are unavailable to you, so I'd suggest opening tickets upstream with the missing modules in question to get builds created. You could probably compile them manually or run them inside of a VM.
Since we're really at the mercy of the upstream packages, and you can still use WordPress without the build tools, there's nothing really we can do here (other than switch to another package, and verify it and all of it's dependencies have linux-arm packages forever too).