Package Details: nodejs-ember-cli 4.0.1-1

Git Clone URL: https://aur.archlinux.org/nodejs-ember-cli.git (read-only, click to copy)
Package Base: nodejs-ember-cli
Description: The ember command line interface
Upstream URL: http://www.ember-cli.com/
Licenses: MIT
Submitter: jhass
Maintainer: jhass
Last Packager: jhass
Votes: 2
Popularity: 0.000000
First Submitted: 2015-05-15 12:39 (UTC)
Last Updated: 2021-12-25 11:09 (UTC)

Latest Comments

bobpaul commented on 2018-06-19 20:42 (UTC) (edited on 2018-06-19 20:54 (UTC) by bobpaul)

I'm getting:

==> Starting package()...
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! network request to https://registry.npmjs.org/ember-cli failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR!     ~/.npm/_logs/2018-06-19T20_41_19_200Z-debug.log
==> ERROR: A failure occurred in package().
    Aborting...

but if I curl <https://registry.npmjs.org/ember-cli> then it returns a bunch of json.

<hr>

I think my issue is related to IPv6. I don't have IPv6 configured on my computer or router, but I notice when I nslookup registry.npmjs.org, I get both IPv4 and IPv6 addresses in the response. I'm able to build the package if I put registry.npmjs.org in my /etc/hosts file using one of the IPv4 addresses that was returned.

diamond29 commented on 2015-11-03 23:29 (UTC)

Seems to be related to the issue here. https://github.com/ember-cli/ember-cli/issues/5018 this command worked for me: npm install ember-cli -g --no-optional

jhass commented on 2015-10-09 22:40 (UTC)

You tried the latest version with this change? https://aur.archlinux.org/cgit/aur.git/commit/?h=nodejs-ember-cli&id=6bbcac6c5336f07c0314e70df19959f04c0fbb82

aabmass commented on 2015-10-09 22:37 (UTC)

Build fails the same way for me too installing this with plain npm install -g ember-cli. Maybe an issue with arch's npm resolving the version of bufferutil?

jokke commented on 2015-09-24 09:46 (UTC)

Build fails: /home/jokke/.cache/aur-packages/nodejs-ember-cli/pkg/nodejs-ember-cli/usr/bin/ember -> /home/jokke/.cache/aur-packages/nodejs-ember-cli/pkg/nodejs-ember-cli/usr/lib/node_modules/ember-cli/bin/ember > bufferutil@1.1.0 install /home/jokke/.cache/aur-packages/nodejs-ember-cli/pkg/nodejs-ember-cli/usr/lib/node_modules/ember-cli/node_modules/bufferutil > node-gyp rebuild make: Entering directory '/home/jokke/.cache/aur-packages/nodejs-ember-cli/pkg/nodejs-ember-cli/usr/lib/node_modules/ember-cli/node_modules/bufferutil/build' CXX(target) Release/obj.target/bufferutil/src/bufferutil.o In file included from ../src/bufferutil.cc:16:0: ../../nan/nan.h:261:25: error: redefinition of ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Local<T>)’ NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Local<T> val) { ^ ../../nan/nan.h:256:25: note: ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Handle<T>)’ previously declared here NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Handle<T> val) { ^ ../../nan/nan.h:661:13: error: ‘node::smalloc’ has not been declared , node::smalloc::FreeCallback callback ^ ../../nan/nan.h:661:35: error: expected ‘,’ or ‘...’ before ‘callback’ , node::smalloc::FreeCallback callback ^ ../../nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(char*, size_t, int)’: ../../nan/nan.h:665:50: error: ‘callback’ was not declared in this scope v8::Isolate::GetCurrent(), data, length, callback, hint); ^ ../../nan/nan.h:665:60: error: ‘hint’ was not declared in this scope v8::Isolate::GetCurrent(), data, length, callback, hint); ^ ../../nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(const char*, uint32_t)’: ../../nan/nan.h:672:67: error: no matching function for call to ‘New(v8::Isolate*, const char*&, uint32_t&)’ return node::Buffer::New(v8::Isolate::GetCurrent(), data, size); ^ In file included from ../src/bufferutil.cc:10:0: /home/jokke/.node-gyp/4.1.0/include/node/node_buffer.h:31:40: note: candidate: v8::MaybeLocal<v8::Object> node::Buffer::New(v8::Isolate*, v8::Local<v8::String>, node::encoding) <near match> NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, ^ /home/jokke/.node-gyp/4.1.0/include/node/node_buffer.h:31:40: note: conversion of argument 3 would be ill-formed: In file included from ../src/bufferutil.cc:16:0: ../../nan/nan.h:672:67: error: invalid conversion from ‘uint32_t {aka unsigned int}’ to ‘node::encoding’ [-fpermissive] return node::Buffer::New(v8::Isolate::GetCurrent(), data, size); ^ In file included from ../src/bufferutil.cc:10:0: /home/jokke/.node-gyp/4.1.0/include/node/node_buffer.h:43:40: note: candidate: v8::MaybeLocal<v8::Object> node::Buffer::New(v8::Isolate*, char*, size_t) <near match> NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, ^ /home/jokke/.node-gyp/4.1.0/include/node/node_buffer.h:43:40: note: conversion of argument 2 would be ill-formed: In file included from ../src/bufferutil.cc:16:0: ../../nan/nan.h:672:67: error: invalid conversion from ‘const char*’ to ‘char*’ [-fpermissive] return node::Buffer::New(v8::Isolate::GetCurrent(), data, size); ^ ../../nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(uint32_t)’: ../../nan/nan.h:676:29: error: could not convert ‘node::Buffer::New(v8::Isolate::GetCurrent(), ((size_t)size))’ from ‘v8::MaybeLocal<v8::Object>’ to ‘v8::Local<v8::Object>’ return node::Buffer::New(v8::Isolate::GetCurrent(), size); ^ ../../nan/nan.h: In function ‘v8::Local<v8::Object> NanBufferUse(char*, uint32_t)’: ../../nan/nan.h:683:12: error: ‘Use’ is not a member of ‘node::Buffer’ return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size); ^ bufferutil.target.mk:92: recipe for target 'Release/obj.target/bufferutil/src/bufferutil.o' failed make: *** [Release/obj.target/bufferutil/src/bufferutil.o] Error 1 make: Leaving directory '/home/jokke/.cache/aur-packages/nodejs-ember-cli/pkg/nodejs-ember-cli/usr/lib/node_modules/ember-cli/node_modules/bufferutil/build' gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23) gyp ERR! stack at emitTwo (events.js:87:13) gyp ERR! stack at ChildProcess.emit (events.js:172:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12) gyp ERR! System Linux 4.1.6-1-ARCH gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /home/jokke/.cache/aur-packages/nodejs-ember-cli/pkg/nodejs-ember-cli/usr/lib/node_modules/ember-cli/node_modules/bufferutil gyp ERR! node -v v4.1.0 gyp ERR! node-gyp -v v3.0.1 gyp ERR! not ok npm ERR! Linux 4.1.6-1-ARCH npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "--user" "root" "-g" "--prefix" "/home/jokke/.cache/aur-packages/nodejs-ember-cli/pkg/nodejs-ember-cli/usr" "ember-cli@1.13.8" npm ERR! node v4.1.0 npm ERR! npm v3.3.3 npm ERR! code ELIFECYCLE npm ERR! bufferutil@1.1.0 install: `node-gyp rebuild` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the bufferutil@1.1.0 install script 'node-gyp rebuild'. npm ERR! This is most likely a problem with the bufferutil package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-gyp rebuild npm ERR! You can get their info via: npm ERR! npm owner ls bufferutil npm ERR! There is likely additional logging output above. npm ERR! Linux 4.1.6-1-ARCH npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "--user" "root" "-g" "--prefix" "/home/jokke/.cache/aur-packages/nodejs-ember-cli/pkg/nodejs-ember-cli/usr" "ember-cli@1.13.8" npm ERR! node v4.1.0 npm ERR! npm v3.3.3 npm ERR! path npm-debug.log.3d487ad1b7f7f788801df9b9941f2205 npm ERR! code ENOENT npm ERR! errno -2 npm ERR! syscall open npm ERR! enoent ENOENT: no such file or directory, open 'npm-debug.log.3d487ad1b7f7f788801df9b9941f2205' npm ERR! enoent This is most likely not a problem with npm itself npm ERR! enoent and is related to npm not being able to find a file. npm ERR! enoent npm ERR! Please include the following file with any support request: npm ERR! /home/jokke/.cache/aur-packages/nodejs-ember-cli/pkg/nodejs-ember-cli/usr/lib/node_modules/npm-debug.log