Impossible d’installer les dépendance

bonjour je suis nouveau et je c pas si c moi qui et mal compris la doc mais je n’arrive pas a installer les dépendance a chaque fois sa s’arrête a 45% je suis sur la v4.0.49 merci pour le partage @sigalou

Bonjour,

Pouvez vous fournir les logs svp

bonjour @nebz

voici le log :

--0%
--10%
Lancement de l'installation/mise à jour des dépendances
--20%
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://www.deb-multimedia.org stretch InRelease
Ign:4 http://ftp.debian.org/debian stretch InRelease
Hit:5 http://ftp.debian.org/debian stretch-updates InRelease
Hit:6 http://ftp.debian.org/debian stretch-backports InRelease
Hit:7 http://ftp.debian.org/debian stretch-proposed-updates InRelease
Hit:8 http://ftp.debian.org/debian stretch Release
Hit:9 https://deb.nodesource.com/node_12.x stretch InRelease
Get:3 https://repo.jeedom.com/odroid stable InRelease [1640 B]
Hit:10 https://oph.mdrjr.net/meveric all InRelease
Hit:11 https://oph.mdrjr.net/meveric stretch InRelease
Err:3 https://repo.jeedom.com/odroid stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9EB92D05446446C
Fetched 1640 B in 3s (500 B/s)
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.jeedom.com/odroid stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9EB92D05446446C
W: Failed to fetch http://repo.jeedom.com/odroid/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9EB92D05446446C
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version (9.20161125).
0 upgraded, 0 newly installed, 0 to remove and 176 not upgraded.
--30%
Version actuelle :
--40%
KO, version obsolète à upgrader
Suppression du Nodejs existant et installation du paquet recommandé
Reading package lists...
Building dependency tree...
Reading state information...
Package 'npm' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 176 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
Package 'nodejs' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 176 not upgraded.
--45%
Utilisation du dépot officiel
## Installing the NodeSource Node.js 12.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://www.deb-multimedia.org stretch InRelease
Ign:4 http://ftp.debian.org/debian stretch InRelease
Hit:5 http://ftp.debian.org/debian stretch-updates InRelease
Hit:6 http://ftp.debian.org/debian stretch-backports InRelease
Hit:7 http://ftp.debian.org/debian stretch-proposed-updates InRelease
Hit:8 http://ftp.debian.org/debian stretch Release
Hit:9 https://deb.nodesource.com/node_12.x stretch InRelease
Get:3 https://repo.jeedom.com/odroid stable InRelease [1640 B]
Hit:10 https://oph.mdrjr.net/meveric all InRelease
Hit:11 https://oph.mdrjr.net/meveric stretch InRelease
Err:3 https://repo.jeedom.com/odroid stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9EB92D05446446C
Fetched 1640 B in 3s (509 B/s)
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.jeedom.com/odroid stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9EB92D05446446C
W: Failed to fetch http://repo.jeedom.com/odroid/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9EB92D05446446C
W: Some index files failed to download. They have been ignored, or old ones used instead.
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_12.x/dists/stretch/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
Warning: apt-key output should not be parsed (stdout is not a terminal)
OK
## Creating apt sources list file for the NodeSource Node.js 12.x repo...
+ echo 'deb https://deb.nodesource.com/node_12.x stretch main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src https://deb.nodesource.com/node_12.x stretch main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you...
+ apt-get update
Hit:1 http://www.deb-multimedia.org stretch InRelease
Hit:2 http://security.debian.org stretch/updates InRelease
Ign:4 http://ftp.debian.org/debian stretch InRelease
Hit:5 http://ftp.debian.org/debian stretch-updates InRelease
Hit:6 http://ftp.debian.org/debian stretch-backports InRelease
Hit:7 http://ftp.debian.org/debian stretch-proposed-updates InRelease
Hit:8 http://ftp.debian.org/debian stretch Release
Hit:9 https://deb.nodesource.com/node_12.x stretch InRelease
Get:3 https://repo.jeedom.com/odroid stable InRelease [1640 B]
Hit:10 https://oph.mdrjr.net/meveric all InRelease
Hit:11 https://oph.mdrjr.net/meveric stretch InRelease
Err:3 https://repo.jeedom.com/odroid stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9EB92D05446446C
Fetched 1640 B in 3s (504 B/s)
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.jeedom.com/odroid stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9EB92D05446446C
W: Failed to fetch http://repo.jeedom.com/odroid/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9EB92D05446446C
W: Some index files failed to download. They have been ignored, or old ones used instead.
## Run `sudo apt-get install -y nodejs` to install Node.js 12.x and npm
## You may also need development tools to build native addons:
sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update && sudo apt-get install yarn
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
nodejs
0 upgraded, 1 newly installed, 0 to remove and 176 not upgraded.
Need to get 12.0 MB of archives.
After this operation, 60.4 MB of additional disk space will be used.
Err:1 https://repo.jeedom.com/odroid stable/main arm64 nodejs arm64 8.9.4-1nodesource1
404  Not Found
E: Failed to fetch https://repo.jeedom.com/odroid/pool/main/n/nodejs/nodejs_8.9.4-1nodesource1_arm64.deb  404  Not Found
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
/var/www/html/plugins/alexaapi/resources/nodejs.sh: line 153: npm: command not found
/var/www/html/plugins/alexaapi/resources/nodejs.sh: line 155: nodejs: command not found
Version actuelle :
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
npm : Depends: nodejs (>= 6.11~) but it is not going to be installed
Depends: node-abbrev (>= 1.1.1~) but it is not going to be installed
Depends: node-ansi-regex (>= 3.0~) but it is not going to be installed
Depends: node-ansistyles (>= 0.1.3~) but it is not going to be installed
Depends: node-aproba (>= 1.2~) but it is not going to be installed
Depends: node-archy (>= 1.0~) but it is not going to be installed
Depends: node-cacache (>= 10.0.4~) but it is not going to be installed
Depends: node-bluebird (>= 3.5.1~) but it is not going to be installed
Depends: node-call-limit (>= 1.1~) but it is not going to be installed
Depends: node-chownr (>= 1.0.1~) but it is not going to be installed
Depends: node-config-chain (>= 1.1.11~) but it is not going to be installed
Depends: node-detect-indent (>= 5.0~) but it is not going to be installed
Depends: node-detect-newline (>= 2.1~) but it is not going to be installed
Depends: node-editor (>= 1.0~) but it is not going to be installed
Depends: node-fs-vacuum (>= 1.2.10~) but it is not going to be installed
Depends: node-fs-write-stream-atomic (>= 1.0.10~) but it is not going to be installed
Depends: node-glob (>= 7.1.2~) but it is not going to be installed
Depends: node-graceful-fs (>= 4.1.11~) but it is not going to be installed
Depends: node-has-unicode (>= 2.0.1~) but it is not going to be installed
Depends: node-hosted-git-info (>= 2.6~) but it is not going to be installed
Depends: node-iferr (>= 0.1.5~) but it is not going to be installed
Depends: node-inflight (>= 1.0.6~) but it is not going to be installed
Depends: node-inherits (>= 2.0.3~) but it is not going to be installed
Depends: node-ini (>= 1.3.5~) but it is not going to be installed
Depends: node-npm-package-arg but it is not going to be installed
Depends: node-promzard but it is not going to be installed
Depends: node-jsonstream (>= 1.3.2~) but it is not going to be installed
Depends: node-json-parse-better-errors (>= 1.0.1~) but it is not going to be installed
Depends: node-lazy-property (>= 1.0~) but it is not going to be installed
Depends: node-libnpx (>= 10.0.1~) but it is not going to be installed
Depends: node-lockfile (>= 1.0.3~) but it is not going to be installed
Depends: node-lru-cache (>= 4.1.1~) but it is not going to be installed
Depends: node-mississippi (>= 3.0~) but it is not going to be installed
Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed
Depends: node-move-concurrently (>= 1.0.1~) but it is not going to be installed
Depends: node-nopt but it is not going to be installed
Depends: node-normalize-package-data (>= 2.4~) but it is not going to be installed
Depends: node-gyp (>= 3.6.2~) but it is not going to be installed
Depends: node-resolve-from (>= 4.0~) but it is not going to be installed
Depends: node-encoding but it is not going to be installed
Depends: node-errno but it is not going to be installed
Depends: node-npmlog (>= 4.1.2~) but it is not going to be installed
Depends: node-once (>= 1.4~) but it is not going to be installed
Depends: node-opener (>= 1.4.3~) but it is not going to be installed
Depends: node-osenv (>= 0.1.5~) but it is not going to be installed
Depends: node-path-is-inside (>= 1.0.2~) but it is not going to be installed
Depends: node-promise-inflight (>= 1.0.1~) but it is not going to be installed
Depends: node-ansi but it is not going to be installed
Depends: node-qw (>= 1.0.1~) but it is not going to be installed
Depends: node-read (>= 1.0.7~) but it is not going to be installed
Depends: node-read-package-json (>= 2.0.13~) but it is not going to be installed
Depends: node-request (>= 2.83~) but it is not going to be installed
Depends: node-retry (>= 0.10.1~) but it is not going to be installed
Depends: node-rimraf (>= 2.6.2~) but it is not going to be installed
Depends: node-safe-buffer (>= 5.1.1~) but it is not going to be installed
Depends: node-semver (>= 5.5~) but it is not going to be installed
Depends: node-sha (>= 2.0.1~) but it is not going to be installed
Depends: node-slide (>= 1.1.6~) but it is not going to be installed
Depends: node-sorted-object (>= 2.0.1~) but it is not going to be installed
Depends: node-from2 but it is not going to be installed
Depends: node-stream-iterate but it is not going to be installed
Depends: node-ssri (>= 5.2.4~) but it is not going to be installed
Depends: node-strip-ansi (>= 4.0~) but it is not going to be installed
Depends: node-tar (>= 4.4~) but it is not going to be installed
Depends: node-text-table (>= 0.2~) but it is not going to be installed
Depends: node-uid-number (>= 0.0.6~) but it is not going to be installed
Depends: node-unique-filename (>= 1.1~) but it is not going to be installed
Depends: node-unpipe (>= 1.0~) but it is not going to be installed
Depends: node-boxen (>= 1.2.1~) but it is not going to be installed
Depends: node-import-lazy but it is not going to be installed
Depends: node-is-npm (>= 1.0~) but it is not going to be installed
Depends: node-latest-version (>= 3.0~) but it is not going to be installed
Depends: node-semver-diff (>= 2.0~) but it is not going to be installed
Depends: node-xdg-basedir (>= 3.0~) but it is not going to be installed
Depends: node-validate-npm-package-name (>= 3.0~) but it is not going to be installed
Depends: node-which (>= 1.3~) but it is not going to be installed
Depends: node-wrappy (>= 1.0.2~) but it is not going to be installed
Depends: node-write-file-atomic (>= 2.3~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
sudo: npm: command not found
--50%
--60%
Installation...
sudo: npm: command not found
chown: cannot access 'node_modules': No such file or directory
--95%
--100%
Installation des dépendances alexaapi terminée, vérifiez qu'il n'y a pas d'erreur

Repo.jeedom qui pose problème, contact le support jeedom core (pas celui du plugin sinon ça arrivera chez le dev qui peut rien y faire) en indiquant ce log lorsque tu essayes d’installer un plug-in qui utilise nodejs, ils corrigeront.

ok merci @nebz pour ton temps :wink:

Heureusement qu’il y a Findus ! Findus !

Ok je sors :wink:

1 « J'aime »

dsl @nebz mais je ne c pas ou poster mon message peut tu m’indique ou stp ? j’ai fait un tour sur le forum et je ne trouve vraiment pas merci d’avance

C’est pas dans le forum c’est directement dans ton jeedom.

J’ai pas de v4 sous la main pour te donner le menu exacte mais cherche un peu cas se trouve dans les menus du haut

a ok je vois c ou encore merci @nebz

Bonjour,
En voulant réinstaller Alexa-api à la suite de l’ erreur « port 3456: Connection refused », je rencontre moi aussi un pb sur l’installation des dépendances.
Quelqu’un peut-il m’aider grâce à la log suivante ?
npm verb type system
npm verb stack FetchError: request to https://registry.npmjs.org/alexa-cookie2/-/alexa-cookie2-2.1.0.tgz failed, reason: connect ENETUNREACH 104.16.24.35:443
npm verb stack at ClientRequest. (/usr/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14)
npm verb stack at ClientRequest.emit (events.js:310:20)
npm verb stack at TLSSocket.socketErrorListener (_http_client.js:426:9)
npm verb stack at TLSSocket.emit (events.js:310:20)
npm verb stack at emitErrorNT (internal/streams/destroy.js:92:8)
npm verb stack at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
npm verb stack at processTicksAndRejections (internal/process/task_queues.js:84:21)
npm verb cwd /var/www/html/plugins/alexaapi/resources
npm verb Linux 4.9.0-12-amd64
npm verb argv « /usr/bin/node » « /usr/bin/npm » « install » « –verbose »
npm verb node v12.16.2
npm verb npm v6.14.4
npm ERR! code ENETUNREACH
npm ERR! errno ENETUNREACH
npm ERR! request to https://registry.npmjs.org/alexa-cookie2/-/alexa-cookie2-2.1.0.tgz failed, reason: connect ENETUNREACH 104.16.24.35:443
npm verb exit [ 1, true ]
npm timing npm Completed in 2578577ms

Bonjour, tu as un problème d’accès à internet, ton dns ou qqch du genre… il arrive pas à se connecter à l’url indiquée

Merci pour ton aide. Je viens de trouver l’origine du problème et l’indique ici au cas où d’autres auraient le même souci : j’ai du changer de carte SIM dans mon routeur Huawei. Je suis passée de SFR à Bouygues. Or Bouygues ne supporte le mode IP v4 + IP v6 et a donc basculé mon routeur ip V6 uniquement. Cela a engendré beaucoup de dysfonctionnements dans mes comm domotiques, dont ce problème, maintenant résolu en configurant mon profil APN pour Bouygues dans le routeur uniquement en V4.

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.