Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some dep updates #631

Merged
merged 1 commit into from
May 22, 2015
Merged

Some dep updates #631

merged 1 commit into from
May 22, 2015

Conversation

Martii
Copy link
Member

@Martii Martii commented May 22, 2015

  • Migrate to newer SPDX v2.x syntax in package.json

See also:

Note(s):

  • Interesting that the newer specification doesn't seem to exist for custom MIT licensing terms which are part of that specification and a few other license types including GPL required Copyright information e.g. not fixed format with the url property seeming to be missing for pointing to the LICENSE content. Refer to local raw LICENSE.* files for exact text including and later revisions of GPL if ever encountered. In other words SPDX doesn't seem to account for this if a change comes through the pipe but LICENSE.* will always supersede.

Post #177 change for migration

* Migrate to newer SPDX v2.x syntax in `package.json`

See also:
* [https://docs.npmjs.com/files/package.json#license](https://docs.npmjs.com/files/package.json#license) ... note deprecation of plural form
* [SPDX license expressions](http://wiki.spdx.org/view/LicenseExpressionFAQ)
* [SPDX license expressions Examples](http://wiki.spdx.org/view/FileNoticeExamples)

Note(s):
* Interesting that the newer specification doesn't seem to exist for custom MIT licensing terms which are part of that specification and a few other license types including GPL required Copyright information e.g. not fixed format with the `url` property seeming to be missing for pointing to the LICENSE content. Refer to local raw LICENSE.* files for exact text including `and later` revisions of GPL if ever encountered. In other words SPDX doesn't seem to account for this if a change comes through the pipe but LICENSE.* will always supersede.
@Martii Martii added migration Use this to indicate that it may apply to an existing or announced migration. CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. labels May 22, 2015
Martii added a commit that referenced this pull request May 22, 2015
@Martii Martii merged commit 722fb8f into OpenUserJS:master May 22, 2015
@Martii Martii deleted the someDepUpdates branch May 22, 2015 19:43
@Martii
Copy link
Member Author

Martii commented May 22, 2015

Fatal deploy error

> [email protected] install /root/tmp/tmp-42629roxhvrk/build/package/node_modules/express-minify/node_modules/node-sass
> node scripts/install.js

Cannot download "https://github.com/sass/node-sass/releases/download/v3.1.2/sunos-x64-11_binding.node": HTTP error 404 

> [email protected] postinstall /root/tmp/tmp-42629roxhvrk/build/package/node_modules/express-minify/node_modules/node-sass
> node scripts/build.js

Building: /opt/local/bin/node node_modules/pangyp/bin/node-gyp rebuild --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
make: Entering directory `/root/tmp/tmp-42629roxhvrk/build/package/node_modules/express-minify/node_modules/node-sass/build'
  CXX(target) Release/obj.target/libsass/src/libsass/ast.o
In file included from ../src/libsass/ast.hpp:34:0,
                 from ../src/libsass/ast.cpp:1:
../src/libsass/units.hpp:39:5: error: expected identifier before numeric constant
../src/libsass/units.hpp:39:5: error: expected '}' before numeric constant
../src/libsass/units.hpp:39:5: error: expected unqualified-id before numeric constant
../src/libsass/units.hpp:62:3: error: 'SassUnit' does not name a type
../src/libsass/units.hpp:63:30: error: 'SassUnit' was not declared in this scope
../src/libsass/units.hpp:63:30: note: suggested alternative:
../src/libsass/units.hpp:22:8: note:   'Sass::SassUnit'
../src/libsass/units.hpp:64:3: error: 'SassUnitType' does not name a type
../src/libsass/units.hpp:66:34: error: 'string' does not name a type
../src/libsass/units.hpp:66:40: error: ISO C++ forbids declaration of 'parameter' with no type [-fpermissive]
../src/libsass/units.hpp:66:49: error: 'string' does not name a type
../src/libsass/units.hpp:66:55: error: ISO C++ forbids declaration of 'parameter' with no type [-fpermissive]
../src/libsass/units.hpp:69:3: error: expected class-name before '{' token
../src/libsass/units.hpp:72:34: error: expected ')' before 'a'
../src/libsass/units.hpp:87:1: error: expected declaration before '}' token
../src/libsass/units.hpp:11:16: warning: 'Sass::PI' defined but not used [-Wunused-variable]
make: *** [Release/obj.target/libsass/src/libsass/ast.o] Error 1make: Leaving directory `/root/tmp/tmp-42629roxhvrk/build/package/node_modules/express-minify/node_modules/node-sass/build'

gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/root/tmp/tmp-42629roxhvrk/build/package/node_modules/express-minify/node_modules/node-sass/node_modules/pangyp/lib/build.js:271:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:810:12)
gyp ERR! System SunOS 5.11
gyp ERR! command "/opt/local/bin/node" "/root/tmp/tmp-42629roxhvrk/build/package/node_modules/express-minify/node_modules/node-sass/node_modules/pangyp/bin/node-gyp" "rebuild" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /root/tmp/tmp-42629roxhvrk/build/package/node_modules/express-minify/node_modules/node-sass
gyp ERR! node -v v0.10.33
gyp ERR! pangyp -v v2.2.0
gyp ERR! not ok 
Build failed
npm ERR! [email protected] postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/build.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! System SunOS 5.11
npm ERR! command "node" "/opt/local/bin/npm" "install" "--loglevel=http"
npm ERR! cwd /root/tmp/tmp-42629roxhvrk/build/package
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.14
npm ERR! code ELIFECYCLE
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /root/tmp/tmp-42629roxhvrk/build/package/npm-debug.log
npm ERR! not ok code 0
error:   Error running command deploy
error:   npm exited with code 1
error:   Nodejitsu Error: Build Failure, please check the build failure above
help:    For help with this error contact Nodejitsu Support:
help:      webchat: <http://webchat.nodejitsu.com/>
help:          irc: <irc://chat.freenode.net/#nodejitsu>
help:        email: <[email protected]>
help:    
help:      Copy and paste this output to a gist (http://gist.github.com/)
info:    Nodejitsu not ok

See #425 for long term solution... sending deploy request to @sizzlemctwizzle ... does however seem to work fine on local production and of course dev testing... possible #441 issue as well.

Martii pushed a commit to Martii/OpenUserJS.org that referenced this pull request May 22, 2015
* Incompatible with nodejitsu at this time

See also:
[this commit](breezewish/express-minify@66a31a6#diff-b9cfc7f2cdf78a7f4b91a753d10865a2L25

Post OpenUserJS#631
Martii referenced this pull request in breezewish/express-minify May 22, 2015
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. migration Use this to indicate that it may apply to an existing or announced migration.
Development

Successfully merging this pull request may close these issues.

1 participant