HTTP error 404 downloading node-sass 4.5.0 binding binary for FreeBSD 11

HiMyNameIsIlNano commented 7 years ago

When I run npm install node-sass on my Freebsd machine I get:

> node-sass@4.5.0 install /usr/home/****/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5.0/freebsd-x64-51_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.0/freebsd-x64-51_binding.node": 

HTTP error 404 Not Found

The file freebsd-x64-51_binding.node does not exist. Where can one find this file?

Regards, Daniele.

saper commented 7 years ago

@rterbush there is a simple script that copies the node-sass-binaries staging area onto the release page via GitHub API.

I had to rebuild my poudriere infrastructure on a another box and simply didn't have time to re-create all the required jails and update the ports. I have physical servers available to do that.

rterbush commented 7 years ago

@saper ok, so if I understand you correctly, you have the resources needed to produce the FreeBSD binaries and there is nothing I can do to help with that.

saper commented 7 years ago

@rterbush but you can try to reproduce my layout and push fixes/updates

saper commented 7 years ago

I have published bindings for node 8 for amd64 and i386 for the 4.5.3 release

saper commented 7 years ago

I have also published bindings for node 4 and node 6 for FreeBSD. Thank you for your patience!

franktopel commented 6 years ago

7 months to publish proper builds so people don't get a 404? Seriously?

xzyfer commented 6 years ago

@franktopel you're more than welcome to contribute the builds.

franktopel commented 6 years ago

I haven't committed on doing that. Had I done so, no way would it have taken 7 months.

xzyfer commented 6 years ago

We'd love to have you co-ordinate with @saper on contributing compatible freebsd binaries.

On 12 Mar. 2018 12:09 am, "Frank Topel" notifications@github.com wrote:

I haven't committed on doing that. Had I done so, no way would it have taken 7 months.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sass/node-sass/issues/1911#issuecomment-372114356, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjZWCSlIX6ssOR8QM1pamdM_PfmivMZks5tdSIKgaJpZM4MHaO2 .

franktopel commented 6 years ago

You refuse to get my point. When you commit to doing something (which I didn't for this purpose, and it's also beyond my field of expertise) then you do stuff in a timely fashion. 7 months for generating some binaries is way too far off from that expectation.

saper commented 6 years ago

Everyone here in the project has full freedom to do things or not to do things. Do you have a contract with node-sass maintainers that spells out the conditions of the commitment, in particular the agreed service level?

iLevye commented 6 years ago

Some old packages returns 404 on github. I dont know how, but using yarn install or yarn add node-sass@4.5.0 successfuly install this package.

xzyfer commented 6 years ago

yarn add node-sass@latest

renanmoraes commented 6 years ago

With me continues the problem when trying to install version 4.7.2 giving the same error. This was the command used, as above in a response here

npm install node-sass --nodedir=/usr/local

node-sass@4.7.2 install /home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.7.2/linux-x64-64_binding.node Cannot download "https://github.com/sass/node-sass/releases/download/v4.7.2/linux-x64-64_binding.node":

HTTP error 404 Not Found

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

node-sass@4.9.0 install /home/renan/projects/tv-clients/node_modules/node-sass node scripts/install.js

Cached binary found at /home/renan/.npm/node-sass/4.9.0/linux-x64-64_binding.node

node-sass@4.7.2 postinstall /home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass node scripts/build.js

Building: /home/renan/.nvm/versions/node/v10.2.1/bin/node /home/renan/projects/tv-clients/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= gyp info it worked if it ends with ok gyp verb cli [ '/home/renan/.nvm/versions/node/v10.2.1/bin/node', gyp verb cli '/home/renan/projects/tv-clients/node_modules/node-gyp/bin/node-gyp.js', gyp verb cli 'rebuild', gyp verb cli '--verbose', gyp verb cli '--libsass_ext=', gyp verb cli '--libsass_cflags=', gyp verb cli '--libsass_ldflags=', gyp verb cli '--libsass_library=' ] gyp info using node-gyp@3.7.0 gyp info using node@10.2.1 | linux | x64 gyp verb command rebuild [] gyp verb command clean [] gyp verb clean removing "build" directory gyp verb command configure [] gyp verb check python checking for Python executable "python2" in the PATH gyp verb which succeeded python2 /usr/bin/python2 gyp verb check python version /usr/bin/python2 -c "import platform; print(platform.python_version());" returned: "2.7.15\n" gyp verb get node dir compiling against specified --nodedir dev files: /usr/local gyp verb build dir attempting to create "build" dir: /home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass/build gyp verb build dir "build" dir needed to be created? /home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass/build gyp verb build/config.gypi creating config file gyp verb build/config.gypi writing out config file: /home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass/build/config.gypi gyp verb config.gypi checking for gypi file: /home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass/config.gypi gyp verb common.gypi checking for gypi file: /home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass/common.gypi gyp verb gyp gyp format was not specified; forcing "make" gyp info spawn /usr/bin/python2 gyp info spawn args [ '/home/renan/projects/tv-clients/node_modules/node-gyp/gyp/gyp_main.py', gyp info spawn args 'binding.gyp', gyp info spawn args '-f', gyp info spawn args 'make', gyp info spawn args '-I', gyp info spawn args '/home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass/build/config.gypi', gyp info spawn args '-I', gyp info spawn args '/home/renan/projects/tv-clients/node_modules/node-gyp/addon.gypi', gyp info spawn args '-I', gyp info spawn args '/usr/local/common.gypi', gyp info spawn args '-Dlibrary=shared_library', gyp info spawn args '-Dvisibility=default', gyp info spawn args '-Dnode_root_dir=/usr/local', gyp info spawn args '-Dnode_gyp_dir=/home/renan/projects/tv-clients/node_modules/node-gyp', gyp info spawn args '-Dnode_lib_file=/usr/local/$(Configuration)/node.lib', gyp info spawn args '-Dmodule_root_dir=/home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass', gyp info spawn args '-Dnode_engine=v8', gyp info spawn args '--depth=.', gyp info spawn args '--no-parallel', gyp info spawn args '--generator-output', gyp info spawn args 'build', gyp info spawn args '-Goutput_dir=.' ] gyp: /usr/local/common.gypi not found (cwd: /home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass) while reading includes of binding.gyp while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: gyp failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/home/renan/projects/tv-clients/node_modules/node-gyp/lib/configure.js:345:16) gyp ERR! stack at ChildProcess.emit (events.js:182:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12) gyp ERR! System Linux 4.16.0-2-amd64 gyp ERR! command "/home/renan/.nvm/versions/node/v10.2.1/bin/node" "/home/renan/projects/tv-clients/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" gyp ERR! cwd /home/renan/projects/tv-clients/node_modules/@ionic/app-scripts/node_modules/node-sass gyp ERR! node -v v10.2.1 gyp ERR! node-gyp -v v3.7.0 gyp ERR! not ok Build failed with error code: 1 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! node-sass@4.7.2 postinstall: node scripts/build.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the node-sass@4.7.2 postinstall script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/renan/.npm/_logs/2018-06-08T17_01_26_387Z-debug.log

xzyfer commented 6 years ago

The release notes for v4.7.2 has a version table that shows which Node versions ares supported.

nschonni commented 6 years ago

This issue was related to building bindings for Debian after a particular release. If you're coming here from search please read https://github.com/sass/node-sass/blob/master/TROUBLESHOOTING.md#404-downloading-bindingnode-file

sass / node-sass

HTTP error 404 downloading node-sass 4.5.0 binding binary for FreeBSD 11 #1911