I’ve been away from the Spark for about a month. Prior to leaving, I was able to compile locally and download to the Spark either wirelessly or via USB. I had written a number of apps and was starting to put together some fun stuff.
As I come back to it, I saw the announcement about the deep update and figured “This ought to be easy, everything was working before”. Well, no.
It appears that my spark-cli is reporting version 0.3.6. npm reports 1.4.1.14. node reports v0.10.29. When I run “sudo npm update -g spark-cli”, I get a spinning wheel for a second or so and then back to the command line. No change to the versions. Running “sudo npm update” returns nearly instantly to the command prompt.
It appears that I’m pointed at the proper repository “https://registry.npmjs.org” (via the sudo npm config list command).
I followed one of the tutorials to install all of this when I set everything up in mid May. However, I can’t remember which.
It must be something where I pulled in a snapshot rather than a repository, but I’m not remembering which. I do remember a long build process for one of the component. dpkg seems to know about nodejs (0.10.29-1chl1~trusty1). But, it doesn’t know anything of npm.
The original reason for the update seems to have faded, because it appears that my core has a black circuit board. But, the fact that I can’t seem to update the spark environment is more troubling at this point.
I found the original installation directory, but this was for v0.10.28. The “npm update spark-cli” did the same immediate response as before. I then moved up in the directory tree (since I’m running on a later version), but there is no other tree. So, I guess that npm itself has updated.
Running “npm update -g spark-cli --verbose” yielded the following.
johnbo@k100rs ~/Projects/node $ npm update -g spark-cli --verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/bin/node',
npm verb cli '/usr/bin/npm',
npm verb cli 'update',
npm verb cli '-g',
npm verb cli 'spark-cli',
npm verb cli '--verbose' ]
npm info using npm@1.4.14
npm info using node@v0.10.29
npm verb node symlink /usr/bin/node
npm verb url raw spark-cli
npm verb url resolving [ 'https://registry.npmjs.org/', './spark-cli' ]
npm verb url resolved https://registry.npmjs.org/spark-cli
npm info trying registry request attempt 1 at 07:37:19
npm verb etag "6EG2K4CCIGXELOFYT0ZX2WVTU"
npm http GET https://registry.npmjs.org/spark-cli
npm http 304 https://registry.npmjs.org/spark-cli
npm verb etag spark-cli from cache
npm info outdated updating []
npm verb exit [ 0, true ]
npm info ok
johnbo@k100rs ~/Projects/node $
The line that suggests that it is updating something, happens in essentially zero time.
It seems like the installation route that I took before must have stranded one or more packages. I guess that the next step would be to try to blow away the entire node installation and all of its packages and try again.
Hmmm, I think that I had created a mess. I found several spark-cli trees, all slightly different. That coupled with a couple of logical links that pointed to out of date versions, made a mess.
In the end, I searched for spark-cli trees, and nuked them with extreme prejudice. Also, all of the links from ‘spark’ to anywhere else. Once all of that was done, the install -g worked and did its magic.
As near as I can tell, everything is working at this point. Thank you for your help.