On Thu, Jan 19, 2017 at 1:55 PM, Gregory Fenton <gregoryfen...@gmail.com> wrote: > > Hi all > First, let me say I love the Cloud9 IDE. So much more user friendly than > Eclipse :) > > Back to topic, I have installed the > bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img image to the flash on the > BBB, no issues at all. > > Once I flashed the image and configured networking I moved straight to > updating the image. > > I have gone to do apt-get update; apt-get upgrade which proceeds fine until > it tries to install node-gyp-202 via c9-core-installer. > Relevant output from apt-get upgrade: > c9-core-installer:Installing: node-gyp-2.0.2 (for c9-core-installer) > /root/.c9/bin/node-gyp -> > /root/.c9/lib/node_modules/node-gyp/bin/node-gyp.js > znode-gyp@2.0.2 /root/.c9/lib/node_modules/node-gyp > ├── semver@4.3.6 > ├── which@1.2.11 (isexe@1.1.2) > ├── osenv@0.1.3 (os-homedir@1.0.2, os-tmpdir@1.0.2) > ├── graceful-fs@3.0.11 (natives@1.1.0) > ├── nopt@3.0.6 (abbrev@1.0.9) > ├── tar@1.0.3 (inherits@2.0.3, block-stream@0.0.9) > ├── fstream@1.0.10 (inherits@2.0.3, graceful-fs@4.1.10) > ├── minimatch@1.0.0 (sigmund@1.0.1, lru-cache@2.7.3) > ├── mkdirp@0.5.1 (minimist@0.0.8) > ├── npmlog@1.2.1 (ansi@0.3.1, gauge@1.2.7, are-we-there-yet@1.0.6) > ├── glob@4.5.3 (inherits@2.0.3, inflight@1.0.6, once@1.4.0, > minimatch@2.0.10) > ├── rimraf@2.5.4 (glob@7.1.1) > ├── path-array@1.0.1 (array-index@1.0.0) > └── request@2.78.0 (is-typedarray@1.0.0, oauth-sign@0.8.2, aws-sign2@0.6.0, > forever-agent@0.6.1, tunnel-agent@0.4.3, caseless@0.11.0, > stringstream@0.0.5, isstream@0.1.2, json-stringify-safe@5.0.1, extend@3.0.0, > aws4@1.5.0, node-uuid@1.4.7, qs@6.3.0, combined-stream@1.0.5, > mime-types@2.1.12, form-data@2.1.1, tough-cookie@2.3.2, hawk@3.1.3, > http-signature@1.1.1, har-validator@2.0.6) > c9-core-installer:Installing: pty.js-0.3.0 (for c9-core-installer) > - >> pty.js@0.3.0 install /root/.c9/lib/node_modules/pty.js >> node-gyp rebuild > > gyp ERR! configure error > gyp ERR! stack Error: This is most likely not a problem with node-gyp or the > package itself and > gyp ERR! stack is related to network connectivity. In most cases you are > behind a proxy or have bad > gyp ERR! stack network settings. > gyp ERR! stack at Request.<anonymous> > (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:193:21) > gyp ERR! stack at Request.emit (events.js:107:17) > gyp ERR! stack at Request.onRequestError > (/usr/lib/node_modules/npm/node_modules/request/request.js:813:8) > gyp ERR! stack at ClientRequest.emit (events.js:107:17) > gyp ERR! stack at TLSSocket.socketErrorListener (_http_client.js:271:9) > gyp ERR! stack at TLSSocket.emit (events.js:129:20) > gyp ERR! stack at net.js:952:16 > gyp ERR! stack at process._tickCallback (node.js:355:11) > gyp ERR! System Linux 4.4.30-ti-r64 > gyp ERR! command "node" > "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" > gyp ERR! cwd /root/.c9/lib/node_modules/pty.js > gyp ERR! node -v v0.12.18 > gyp ERR! node-gyp -v v3.4.0 > gyp ERR! not ok > npm ERR! Linux 4.4.30-ti-r64 > npm ERR! argv "/root/.c9/node/bin/node" "/root/.c9/node/bin/npm" "install" > "-g" "--unsafe-perm=true" "--progress=false" "--loglevel=error" "--prefix" > "/root/.c9" "pty.js@0.3.0" > npm ERR! node v0.12.18 > npm ERR! npm v2.15.11 > npm ERR! code ELIFECYCLE
"ELIFECYCLE" - i was hoping v0.12.x would "still work" for a little while longer.. (EOL december 31st, 2016, 20 days ago..) Option 1: (if you have important stuff you don't want to loose) sudo sed -i -e 's:node_0.12:node_4.x:g' /etc/apt/sources.list sudo apt update sudo apt install nodejs --reinstall sudo apt install c9-core-installer --reinstall Option 2: Reflash (nodejs v4.x is installed by default now..) https://rcn-ee.net/rootfs/bb.org/testing/2017-01-15/lxqt-4gb/ Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYgHu8dn0nSmdj5q2v3%2BHjL5OE9oKHnWkGRQaLrE2nnPPA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
