Update js-controller - "nodejs is NOT correctly installed"
-
@thomas-braun Ich versuch mich mal nun wieder nach oben zu hangeln..
sudo -H -u iobroker npm install iobroker.js-controllersagt nun:
npm WARN skipping integrity check for git dependency ssh://git@github.com/DrozmotiX/ioBroker.esphome.git npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated xmldom@0.1.16: Deprecated due to CVE-2021-21366 resolved in 0.5.0 npm ERR! code 6 npm ERR! path /opt/iobroker/node_modules/iobroker.vis-google-fonts npm ERR! command failed npm ERR! command sh -c node main.js --install npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-03T12_24_45_263Z-debug-0.logopen Request’s Past, Present and Future #3142
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
sehr seltsam... Beim 2.
sudo -H -u iobroker npm install iobroker.js-controllerwurde der js-controller nun installiert...
-
Was für ein Kampf
Aber letztendlich doch erfolgreich - JS-Controller wurde erfolgreich geupdated.@Thomas-Braun Vielen, vielen Dank für deine Hilfe und deine unendliche Geduld
-
-
@thomas-braun
Das sieht es jetzt prinzipiell besser aus...Errors in npm tree: npm ERR! code ELSPROBLEMS npm ERR! invalid: iobroker.vis-materialdesign@0.2.62 /opt/iobroker/node_modules/iobroker.vis-materialdesign npm ERR! invalid: socksv5@0.0.6 /opt/iobroker/node_modules/socksv5 npm ERR! invalid: xmlbuilder@0.4.2 /opt/iobroker/node_modules/xmlbuilder npm ERR! missing: cli@0.4.x, required by ipv6@3.1.1 npm ERR! missing: cliff@0.1.x, required by ipv6@3.1.1 npm ERR! A complete log of this run can be found in: /home/jonny/.npm/_logs/2023-11-03T15_35_17_056Z-debug-0.log *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.12 admin: 6.12.0 javascript: 7.1.4 npm ERR! code ELSPROBLEMS npm ERR! invalid: iobroker.vis-materialdesign@0.2.62 /opt/iobroker/node_modules/iobroker.vis-materialdesign npm ERR! A complete log of this run can be found in: /home/jonny/.npm/_logs/2023-11-03T15_35_25_269Z-debug-0.log Adapters from github: 1Aber den iobroker.vis-materialdesign kann ich nicht entfernen, da scheinbar 50% meiner Vis darauf basieren.
-
-
jonny@ioBroker-V2:~$ iob upgrade vis-materialdesign@0.5.9 Adapter "vis-materialdesign" is not in the repository and cannot be updated.Der ist (vermutlich) von hier: https://github.com/Scrounger/ioBroker.vis-materialdesign/blob/master/README.md
-
Dann zieh das aus npm / Beta rein. Der hat es nie nach Stable gebracht:
vis-materialdesign github: 0.5.94 latest: 0.5.9 for 29 months stable: -.-.- -
socksv5, ipv6 usw wirst du vermultich nicht gefixt bekommen, das ist alles zu alt und ungewartet.
cd /opt/iobroker && npm ls xmlbuilderkann man vielleicht noch angehen.
-
@thomas-braun said in Update js-controller - "nodejs is NOT correctly installed":
socksv5, ipv6 usw wirst du vermultich nicht gefixt bekommen, das ist alles zu alt und ungewartet.
cd /opt/iobroker && npm ls xmlbuilderkann man vielleicht noch angehen.
socksv5 und ipv6 kommen wahrscheinlich via Telegram Adapter rein.
Da ist was im Anmarsch. Wir haben heute entschieden den socks Proxy support aus dem Telegram Adapter rauszuschmeißen da die entsprechenden Module total veraltet sind und kein 1:1 Ersatz existiert. Falls ggF ein zu großer Aufschrei kommt müssen wir Aifwand setzen um eine Ersatzlösung zu implementieren - aber derzeit sind Resoiurcen eher knapp ...
