Interesting even with LINK nodes

General
21

Ubuntu:

me@me-desktop:~$ apt-cache policy nodejs
nodejs:
  Installed: 8.16.0-1nodesource1
  Candidate: 8.16.0-1nodesource1
  Version table:
 *** 8.16.0-1nodesource1 500
        500 https://deb.nodesource.com/node_8.x bionic/main amd64 Packages
        100 /var/lib/dpkg/status
     8.10.0~dfsg-2ubuntu0.4 500
        500 http://au.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
     8.10.0~dfsg-2ubuntu0.2 500
        500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages
     8.10.0~dfsg-2 500
        500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
me@me-desktop:~$

RPI (one of them. The other is hemraging (?spelling) with the update)

pi@TelePi:~ $ apt-cache policy nodejs
nodejs:
  Installed: (none)
  Candidate: 8.11.1~dfsg-2~bpo9+1
  Version table:
     8.11.1~dfsg-2~bpo9+1 500
        500 http://archive.raspberrypi.org/debian stretch/main armhf Packages
     4.8.2~dfsg-1 500
        500 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages
pi@TelePi:~ $
22

Is that the original issue or why nodejs was apparently downgraded?

23

The link issue that is the subject of this thread,

24

My request for the apt-cache command was related to why the script apparently downgraded nodejs.

25

The script wouldn't. If it finds anything more recent than 8.11.1 (the old debian apt install) it leaves it alone.

26

That's what I thought, but apparently (alledgedly?) something did.

27

On a side note I sometimes see odd things on the forum. Andrew's post showing the apt-cache results only just appeared, long after later messages. It has put it in the right place chronologically but it did not appear immediately. This has caused me confusion several times.

28

(Innocent bystander)

I post pictures with what I hope is needed. If they don't appear......

Could be the NBN and the great speed is (doesn't) have? (Aussie sarcasm)

29

npm -g === Global - needs sudo.

npm without -g === Local - should never use sudo.

You should never use -g unless you know that you need it.

That will generally only be if you need a system-wide command from the installed package. With Node-RED, installing with -g gives you a global node-red command for example. You can also install Node-RED locally but that is a different discussion.

With Node-RED, local installations of supporting packages (that provide nodes) should always happen in the userDir folder. This is normally /home/pi/.node-red AKA ~/.node-red.

30

Yeah....

Ok.

I have updated 3 RPIs to 0.20.5

My main one is not playing the game.

Given they were all the same for install, that is a bit annoying.

And I did the same command from the same place in them all.

~/.node-red

31

And what happened (with -g it doesn't matter where you do it from)?

32

All the ones worked.

They installed the new NR and worked.

(Stopping/starting NR may have happened.)

This one...... The pain in the a$$ one..... Now just "hangs".

(See New thread)