Urgent: node.lib not distributed for v0.8.27

[brianreavis]

The dist files for 0.8.27 are missing node.lib (32 & 64bit). All other releases seem to have it. This is breaking node-gyp builds. For example, on Appveyor:

C:\projects\node-gdal>node "C:\Program Files (x86)\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild --name=gdal --configuration=Release --module_name=gdal --version=0.0.1 --patch=1 --runtime=node --node_abi=v8-3.11 --platform=win32 --target_platform=win32 --arch=ia32 --target_arch=ia32 --module_main=./lib/gdal.js --host=https://node-gdal.s3-us-west-1.amazonaws.com/ --module_path=C:\projects\node-gdal\lib\binding --remote_path=v0.0.1/ --package_name=v8-3.11-win32-ia32.tar.gz --staged_tarball=build\stage\v0.0.1\v8-3.11-win32-ia32.tar.gz --hosted_path=https://node-gdal.s3-us-west-1.amazonaws.com/v0.0.1/ --hosted_tarball=https://node-gdal.s3-us-west-1.amazonaws.com/v0.0.1/v8-3.11-win32-ia32.tar.gz  
106 gyp http GET http://nodejs.org/dist/v0.8.27/node-v0.8.27.tar.gz
107 gyp http 200 http://nodejs.org/dist/v0.8.27/node-v0.8.27.tar.gz
108 gyp http GET http://nodejs.org/dist/v0.8.27/node.lib
109 gyp http GET http://nodejs.org/dist/v0.8.27/x64/node.lib
110 gyp http 404 http://nodejs.org/dist/v0.8.27/node.lib
111 gyp WARN install got an error, rolling back install
112 gyp http 404 http://nodejs.org/dist/v0.8.27/x64/node.lib
113 gypnpm ERR! weird error 1
114 Command exited with code 1

Relevant links:
http://nodejs.org/dist/v0.8.27/node.lib
http://nodejs.org/dist/v0.8.27/x64/node.lib

[TooTallNate]

+1 @tjfontaine please upload this file

[springmeyer]

Bump, this is breaking many builds for me as well.

[springmeyer]

This is blocking any use of node v0.8 on appveyor (an increasingly common tool, like travis, for testing node.js modules) because of this appveyor limitation: http://help.appveyor.com/discussions/problems/464-be-able-to-control-nodejs-patch-version

[tjfontaine]

I'm rerunning the builds, so I can upload the .lib's -- cutting a new 0.8 will require understanding how to fix the semver bug in an acceptable manner

[tjfontaine]

These have been uploaded and signed in a separate shasum file

http://nodejs.org/dist/v0.8.27/SHASUMS256-win.txt.asc

http://nodejs.org/dist/v0.8.27/SHASUMS-win.txt.asc

[tjfontaine]

@TooTallNate does this resolve the current builds for 0.8?

[TooTallNate]

@tjfontaine Waiting for the output to complete from here, but ya everything looks good in the dist dir now AFAICT.

[isaacs]

cutting a new 0.8 will require understanding how to fix the semver bug in an acceptable manner

Which semver bug are you referring to?

If you mean the use of ^ as a version range selector (as well as the inability for users of Node v0.8 to publish packages or log into the npm registry), can you please comment on #7797 with some specific details as to why that manner isn't acceptable?

[TooTallNate]

v0.8.27 is good to me as of now, so gonna close this issue.

It would be good to have npm on v0.8 not be crippled, but that's a topic for a separate thread.