Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter

[Thomas Braun]

@smizi sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

Setting up nodejs (18.17.1-deb-1nodesource1) ...
Processing triggers for man-db (2.9.4-2) ...

Danach geht es doch noch weiter. 100%ig. Und wenn es nur die neue Eingabezeile ist. Die möchte ich aber sehen, damit ich weiß bis wo das mit welchen Meldungen gelaufen ist.

[Smizi]

@thomas-braun leider nein, das ist alles...sorry```
pi@raspberrypi:~ $ sudo apt install --reinstall nodejs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 28.1 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_18.x bullseye/main arm64 nodejs arm64 18.17.1-deb-1nodesource1 [28.1 MB]
Fetched 28.1 MB in 3s (10.1 MB/s)
(Reading database ... 59608 files and directories currently installed.)
Preparing to unpack .../nodejs_18.17.1-deb-1nodesource1_arm64.deb ...
Unpacking nodejs (18.17.1-deb-1nodesource1) over (18.17.1-deb-1nodesource1) ...
Setting up nodejs (18.17.1-deb-1nodesource1) ...
Processing triggers for man-db (2.9.4-2) ...
pi@raspberrypi:~ $

[Thomas Braun]

@smizi sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

1 not upgraded.

Welches Paket ist das?

sudo apt update
sudo apt full-upgrade

[Smizi]

@thomas-braun sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

sudo apt full-upgrade

Sorry, ich verstehe nicht ganz:

pi@raspberrypi:~ $ sudo apt update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Get:5 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
Hit:6 https://deb.nodesource.com/node_18.x bullseye InRelease
Hit:7 https://apt.grafana.com stable InRelease
Err:5 https://repos.influxdata.com/debian bullseye InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
Fetched 7,040 B in 2s (4,558 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
W: Some index files failed to download. They have been ignored, or old ones used instead.
pi@raspberrypi:~ $ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
grafana
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 80.4 MB of archives.
After this operation, 10.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 https://apt.grafana.com stable/main arm64 grafana arm64 10.0.3 [80.4 MB]
Fetched 80.4 MB in 10s (7,797 kB/s)
Reading changelogs... Done
(Reading database ... 59608 files and directories currently installed.)
Preparing to unpack .../grafana_10.0.3_arm64.deb ...
Unpacking grafana (10.0.3) over (9.3.2) ...
Setting up grafana (10.0.3) ...
Installing new version of config file /etc/init.d/grafana-server ...
Installing new version of config file /usr/lib/systemd/system/grafana-server.service ...
Restarting grafana-server service... OK
pi@raspberrypi:~ $

[DJMarc75]

@smizi bitte alles immer in Codetags posten

[Thomas Braun]

@smizi

Okay, war grafana.

Dann fällt mir aber auch nix mehr dazu ein.

[Smizi]

@djmarc75 sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

@smizi bitte alles immer in Codetags posten

Sorry, mein Fehler

[Smizi]

@thomas-braun
kann ich noch irgendwas tuen, oder was wäre deine Empfehlung?

Gibt es einen bezahlbaren Service via IOB-Projkt, wo ggfs. nochwas geht?

[Thomas Braun]

@smizi

Installier es flugs neu und lass diesmal unnötigen Kram von der Kiste.
Backup des ioBrokers hast du ja.

[Smizi]

@thomas-braun hm, ok und Danke!