Bonjour,
je suis entrain de migrer Jeedom d’un Z83II sous debian vers une Freebox Delta.
Je suis pratiquement arrivé au bout, reste les dépendances des plugins caméra et gsh qui ne s’installent pas.
Ni en utilisant une sauvegarde du Z83II, ni en partant d’une installation propre.
Avez-vous une idée?
Log plugin caméra:
>Launch install of camera dependancy
> Hit:1 http://security.debian.org buster/updates InRelease
> Hit:2 http://deb.debian.org/debian buster InRelease
> Hit:3 http://deb.debian.org/debian buster-updates InRelease
> Hit:4 http://deb.debian.org/debian buster-backports InRelease
> Reading package lists...
> E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
> E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
> E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
> E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
> E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
> Everything is successfully installed!
Log plugin gsh:
> ********************************************************
> * Installation des dépendances *
> ********************************************************
> WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
> Hit:1 http://security.debian.org buster/updates InRelease
> Hit:2 http://deb.debian.org/debian buster InRelease
> Hit:3 http://deb.debian.org/debian buster-updates InRelease
> Hit:4 http://deb.debian.org/debian buster-backports InRelease
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 169 packages can be upgraded. Run 'apt list --upgradable' to see them.
> E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
> /var/www/html/plugins/gsh/core/class/../../resources/install_apt.sh: line 10: ${PROGRESS_FILE}: ambiguous redirect
> Nodejs non installé
> KO, version obsolète à upgrader
> Suppression du Nodejs existant et installation du paquet recommandé
> E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
> /var/www/html/plugins/gsh/core/class/../../resources/install_apt.sh: line 25: $LOG: ambiguous redirect
> 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 buster/updates InRelease
> Hit:2 http://deb.debian.org/debian buster InRelease
> Hit:3 http://deb.debian.org/debian buster-updates InRelease
> Hit:4 http://deb.debian.org/debian buster-backports InRelease
> Reading package lists...
> Confirming "buster" is supported...
> curl -sLf -o /dev/null 'https://deb.nodesource.com/node_12.x/dists/buster/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 buster main' > /etc/apt/sources.list.d/nodesource.list
> echo 'deb-src https://deb.nodesource.com/node_12.x buster main' >> /etc/apt/sources.list.d/nodesource.list
> Running `apt-get update` for you...
> apt-get update
> Hit:1 http://security.debian.org buster/updates InRelease
> Hit:2 http://deb.debian.org/debian buster InRelease
> Hit:3 http://deb.debian.org/debian buster-updates InRelease
> Hit:4 http://deb.debian.org/debian buster-backports InRelease
> Get:5 https://deb.nodesource.com/node_12.x buster InRelease [4584 B]
> Get:6 https://deb.nodesource.com/node_12.x buster/main arm64 Packages [766 B]
> Fetched 5350 B in 2s (2758 B/s)
> Reading package lists...
> 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
> E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
> /var/www/html/plugins/gsh/core/class/../../resources/install_apt.sh: line 38: nodejs: command not found
> Version actuelle :
> E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
> sudo: npm: command not found
> ********************************************************
> * Installation terminée *
> ********************************************************