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 220.127.116.11. 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.
Anyone got a clue what I’ve done wrong?