Erreur Lors des maj de l'Os Debian Bulleye via le MAJ OS Jeedom

Lors de MAJ de l’OS via la fonction Centre de Mise a Jour /OS;Package il y a des message Warning come

  • WARNING: Error parsing dependencies of gpg
  • WARNING: Running pip as the ‹ root › user ca…
    et d’autre Error
  • ERROR: pip’s dependency resolver does not currently take into account …
  • Qui se traduisent au bout d’un moment en arret du procesus

Y a t il quelque chose a faire ou est ce hors Jeedom
Cdlt

Copy du log

"
+ echo '*******************Begin of package upgrade type pip3******************'
*******************Begin of package upgrade type pip3******************
+ sudo python3 -m pip install --force-reinstall --upgrade importlib-metadata
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting importlib-metadata
  Downloading https://www.piwheels.org/simple/importlib-metadata/importlib_metadata-8.4.0-py3-none-any.whl (26 kB)
Collecting zipp>=0.5 (from importlib-metadata)
  Using cached https://www.piwheels.org/simple/zipp/zipp-3.20.1-py3-none-any.whl (9.0 kB)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: zipp, importlib-metadata
  Attempting uninstall: zipp
    Found existing installation: zipp 3.20.1
    Uninstalling zipp-3.20.1:
      Successfully uninstalled zipp-3.20.1
  Attempting uninstall: importlib-metadata
    Found existing installation: importlib-metadata 4.13.0
    Uninstalling importlib-metadata-4.13.0:
      Successfully uninstalled importlib-metadata-4.13.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
gpiozero 2.0.1 requires importlib-metadata~=4.6; python_version < "3.10", but you have importlib-metadata 8.4.0 which is incompatible.
Successfully installed importlib-metadata-8.4.0 zipp-3.20.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ sudo python3 -m pip install --force-reinstall --upgrade importlib-resources
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting importlib-resources
  Downloading https://www.piwheels.org/simple/importlib-resources/importlib_resources-6.4.4-py3-none-any.whl (35 kB)
Collecting zipp>=3.1.0 (from importlib-resources)
  Using cached https://www.piwheels.org/simple/zipp/zipp-3.20.1-py3-none-any.whl (9.0 kB)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: zipp, importlib-resources
  Attempting uninstall: zipp
    Found existing installation: zipp 3.20.1
    Uninstalling zipp-3.20.1:
      Successfully uninstalled zipp-3.20.1
  Attempting uninstall: importlib-resources
    Found existing installation: importlib-resources 5.13.0
    Uninstalling importlib-resources-5.13.0:
      Successfully uninstalled importlib-resources-5.13.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
gpiozero 2.0.1 requires importlib-metadata~=4.6; python_version < "3.10", but you have importlib-metadata 8.4.0 which is incompatible.
gpiozero 2.0.1 requires importlib-resources~=5.0; python_version < "3.10", but you have importlib-resources 6.4.4 which is incompatible.
Successfully installed importlib-resources-6.4.4 zipp-3.20.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ sudo python3 -m pip install --force-reinstall --upgrade picamera2
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting picamera2
  Using cached https://www.piwheels.org/simple/picamera2/picamera2-0.3.18-py3-none-any.whl (76 kB)
Collecting numpy (from picamera2)
  Using cached numpy-2.0.2-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (62 kB)
Collecting PiDNG (from picamera2)
  Using cached pidng-4.0.9.tar.gz (21 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Collecting piexif (from picamera2)
  Using cached https://www.piwheels.org/simple/piexif/piexif-1.1.3-py2.py3-none-any.whl (20 kB)
Collecting pillow (from picamera2)
  Using cached pillow-10.4.0-cp39-cp39-manylinux_2_28_aarch64.whl.metadata (9.2 kB)
Collecting simplejpeg (from picamera2)
  Using cached simplejpeg-1.7.4-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (30 kB)
Collecting v4l2-python3 (from picamera2)
  Using cached https://www.piwheels.org/simple/v4l2-python3/v4l2_python3-0.3.5-py3-none-any.whl (22 kB)
Collecting python-prctl (from picamera2)
  Using cached python-prctl-1.8.1.tar.gz (28 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'error'
  error: subprocess-exited-with-error
  
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [1 lines of output]
      You need to install libcap development headers to build this module
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
+ sudo python3 -m pip install --force-reinstall --upgrade pycups
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting pycups
  Using cached pycups-2.0.4.tar.gz (65 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Building wheels for collected packages: pycups
  Building wheel for pycups (setup.py): started
  Building wheel for pycups (setup.py): finished with status 'error'
  error: subprocess-exited-with-error
  
  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      In file included from cupsconnection.c:22:
      cupsconnection.h:26:10: fatal error: cups/http.h: No such file or directory
         26 | #include <cups/http.h>
            |          ^~~~~~~~~~~~~
      compilation terminated.
      error: command '/usr/bin/aarch64-linux-gnu-gcc' failed with exit code 1
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pycups
  Running setup.py clean for pycups
Failed to build pycups
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (pycups)
+ sudo python3 -m pip install --force-reinstall --upgrade pysmbc
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting pysmbc
  Using cached pysmbc-1.0.25.1.tar.gz (33 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'error'
  error: subprocess-exited-with-error
  
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [20 lines of output]
      Package smbclient was not found in the pkg-config search path.
      Perhaps you should add the directory containing `smbclient.pc'
      to the PKG_CONFIG_PATH environment variable
      No package 'smbclient' found
      Package smbclient was not found in the pkg-config search path.
      Perhaps you should add the directory containing `smbclient.pc'
      to the PKG_CONFIG_PATH environment variable
      No package 'smbclient' found
      Package smbclient was not found in the pkg-config search path.
      Perhaps you should add the directory containing `smbclient.pc'
      to the PKG_CONFIG_PATH environment variable
      No package 'smbclient' found
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-qey7io94/pysmbc_0c77fe542fae4927acabfe5454d5638c/setup.py", line 120, in <module>
          define_macros=pkgconfig_Dversion("smbclient"),
        File "/tmp/pip-install-qey7io94/pysmbc_0c77fe542fae4927acabfe5454d5638c/setup.py", line 85, in pkgconfig_Dversion
          ver = str(int(vers[0]))
      ValueError: invalid literal for int() with base 10: ''
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
+ sudo python3 -m pip install --force-reinstall --upgrade python-prctl
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting python-prctl
  Using cached python-prctl-1.8.1.tar.gz (28 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'error'
  error: subprocess-exited-with-error
  
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [1 lines of output]
      You need to install libcap development headers to build this module
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
+ sudo python3 -m pip install --force-reinstall --upgrade RPi.GPIO
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting RPi.GPIO
  Using cached RPi.GPIO-0.7.1-cp39-cp39-linux_aarch64.whl
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: RPi.GPIO
  Attempting uninstall: RPi.GPIO
    Found existing installation: RPi.GPIO 0.7.0
error: uninstall-distutils-installed-package

× Cannot uninstall RPi.GPIO 0.7.0
╰─> It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.
+ sudo python3 -m pip install --force-reinstall --upgrade systemd-python
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting systemd-python
  Using cached systemd-python-235.tar.gz (61 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'error'
  error: subprocess-exited-with-error
  
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [12 lines of output]
      Cannot find libsystemd or libsystemd-journal:
      
      Package libsystemd was not found in the pkg-config search path.
      Perhaps you should add the directory containing `libsystemd.pc'
      to the PKG_CONFIG_PATH environment variable
      No package 'libsystemd' found
      
      Package libsystemd-journal was not found in the pkg-config search path.
      Perhaps you should add the directory containing `libsystemd-journal.pc'
      to the PKG_CONFIG_PATH environment variable
      No package 'libsystemd-journal' found
      
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
+ sudo python3 -m pip install --force-reinstall --upgrade zeroconf
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting zeroconf
  Using cached zeroconf-0.133.0.tar.gz (171 kB)
  Installing build dependencies: started
  Building wheel for zeroconf (pyproject.toml): still running...
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
  Preparing metadata (pyproject.toml): started
  Preparing metadata (pyproject.toml): finished with status 'done'
Collecting async-timeout>=3.0.0 (from zeroconf)
  Using cached https://www.piwheels.org/simple/async-timeout/async_timeout-4.0.3-py3-none-any.whl (5.7 kB)
Collecting ifaddr>=0.1.7 (from zeroconf)
  Using cached https://www.piwheels.org/simple/ifaddr/ifaddr-0.2.0-py3-none-any.whl (12 kB)
Building wheels for collected packages: zeroconf
  Building wheel for zeroconf (pyproject.toml): started
  Building wheel for zeroconf (pyproject.toml): still running...
  Building wheel for zeroconf (pyproject.toml): still running...
"
1 « J'aime »

Bonjour,

Il ne faut pas (et ce n’est pas nécessaire dans 99% des cas) utliser cette page Jeedom. Donc si cela ne fonctionne pas ce n’est pas important.

J’espère que tu n’as rien cassé sur ton système …

Pourquoi cette page est présente ? n’est-il pas préférable de la sortir et de laisser les utilisateurs faire les majs en SSH ?

Ou mettre au moins un message d’alerte en rouge sur les risques pris.

On voit de plus en plus d’users ayant cliqué ici sans savoir ce qu’ils font et surtout comment réparer ensuite.

Bonjour,

Je suis d’accord, on arrête pas de dire qu’il ne faut pas utiliser cette page, et de plus en plus d’utilisateurs cliquent dessus.

Peut-être laisser la page pour information, mais supprimer les boutons pour lancer les mises à jour ?

Car au delà de ne pas fonctionner dans certains cas, cela peut rendre jeedom inopérant :frowning:

TiTidom.

Bonjour,

il me semble que Loic avait parlé de la supprimer.

Bonjour,

Il manque la page santé… comme d’habitude.


Concernant cette page:

  • pour les maj apt c’est fonctionnel (ca n’empêche pas de comprendre ce qu’on fait)
  • pour les maj python, avec deb12 ca sera plus facilement utilisable car le core gère les dépendances pour chaque plugin dans un venv donc il n’y a plus de risque de casser le système.
    Cette page reprendra plus d’intérêt du coup
2 « J'aime »

Ou alors la déplacer vers l’onglet OS/DB de la config qui à le disclaimer qui va bien.