Dépendances ne s'installent pas sous debian 12

Bonjour ,
J’ai un soucis avec jeedom qui est sous proxmox et le plugin Bléa.
J’ai partagé une clé bluetooth sur la VM JEEDOM.
Qui est bien reconnu par jeedom quand je regarde en ssh

quand je fais sudo blescan -t 5
il détecte bien des équipements

jeedom@Jeedom:~$ sudo blescan -t 5
Scanning for devices...
    Device (new): e3:58:1b:4f:56:dd (random), -62 dBm
        Flags: <06>
        Complete 16b Services: <0000fcb9-0000-1000-8000-00805f9b34fb>
        Tx Power: <02>
        Manufacturer: <270b2808039f4115f2802a62e92280>
        Complete Local Name: 'DoorLocker'
    Device (new): c3:88:b2:a2:3e:0e (random), -71 dBm
        Flags: <06>
        Complete Local Name: 'vuart:ktunnel'
        Manufacturer: <270b0000>
    Device (new): 4d:d1:5f:5e:eb:64 (random), -73 dBm (not connectable)
        Complete 16b Services: <0000fe9f-0000-1000-8000-00805f9b34fb>
        16b Service Data: <9ffe0000000000000000000000000000000000000000>
        Manufacturer: <e0000099ca8ea128>
    Device (new): d8:80:3c:c8:df:05 (public), -79 dBm
        Flags: <02>
        Manufacturer: <570102ffffffffffffffffffffffffffffffff03d8803cc8df05>
        Complete Local Name: 'Amazfit Bip 6'
        Incomplete 16b Services: <0000fee0-0000-1000-8000-00805f9b34fb>
        Appearance: <c000>
    Device (new): 4c:65:a8:d5:77:d2 (public), -83 dBm
        Flags: <06>
        16b Service Data: <fffff971b04cbbbb>
        Complete Local Name: 'MJ_HT_V1'
        Complete 16b Services: <0000180f-0000-1000-8000-00805f9b34fb,0000180a-0000-1000-8000-00805f9b34fb>
    Device (new): 44:68:0f:8b:5f:06 (random), -87 dBm
        Flags: <06>
        16b Service Data: <aafe40f3498c4cac08457f378f45de5db99dc7c236f855bf>

quand je lance les dépendances j’ai toujours dans démon :
Dépendance non installé

Ci dessous le log


********************************************************
*			 Installation des dépendances			 *
********************************************************
Atteint :1 http://security.debian.org/debian-security bookworm-security InRelease
Atteint :2 http://deb.debian.org/debian bookworm InRelease
Atteint :3 http://deb.debian.org/debian bookworm-updates InRelease
Atteint :4 http://phoscon.de/apt/deconz bookworm-beta InRelease
Atteint :5 https://deb.nodesource.com/node_22.x nodistro InRelease
Lecture des listes de paquets…
W: http://phoscon.de/apt/deconz/dists/bookworm-beta/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Lecture des listes de paquets…
Construction de l'arbre des dépendances…
Lecture des informations d'état…
E: Impossible de trouver le paquet libtiff5
Lecture des listes de paquets…
Construction de l'arbre des dépendances…Complété
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Lecture des listes de paquets…
E: Problème de renommage du fichier /var/cache/apt/pkgcache.bin.r0HEXx en /var/cache/apt/pkgcache.bin - rename (2: Aucun fichier ou dossier de ce type)
W: Vous pouvez lancer « apt-get update » pour corriger ces problèmes.
E: Le fichier de cache des paquets est corrompu
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Clonage dans 'bluepy'...
/usr/lib/python3/dist-packages/setuptools/dist.py:775: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
warnings.warn(
running build
running build_py
Working dir is /tmp/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
creating build
creating build/lib
creating build/lib/bluepy
copying bluepy/thingy52.py -> build/lib/bluepy
copying bluepy/scanner.py -> build/lib/bluepy
copying bluepy/sensortag.py -> build/lib/bluepy
copying bluepy/blescan.py -> build/lib/bluepy
copying bluepy/get_services.py -> build/lib/bluepy
copying bluepy/scan_fuzz.py -> build/lib/bluepy
copying bluepy/__init__.py -> build/lib/bluepy
copying bluepy/btle.py -> build/lib/bluepy
copying bluepy/bluepy-helper -> build/lib/bluepy
copying bluepy/uuids.json -> build/lib/bluepy
copying bluepy/bluez-src.tgz -> build/lib/bluepy
copying bluepy/bluepy-helper.c -> build/lib/bluepy
copying bluepy/version.h -> build/lib/bluepy
copying bluepy/Makefile -> build/lib/bluepy
/usr/lib/python3/dist-packages/setuptools/dist.py:775: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
warnings.warn(
running install
/usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
running bdist_egg
running egg_info
creating bluepy.egg-info
writing bluepy.egg-info/PKG-INFO
writing dependency_links to bluepy.egg-info/dependency_links.txt
writing entry points to bluepy.egg-info/entry_points.txt
writing top-level names to bluepy.egg-info/top_level.txt
writing manifest file 'bluepy.egg-info/SOURCES.txt'
reading manifest file 'bluepy.egg-info/SOURCES.txt'
adding license file 'LICENSE.txt'
writing manifest file 'bluepy.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
Working dir is /tmp/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
copying bluepy/bluepy-helper -> build/lib/bluepy
copying bluepy/version.h -> build/lib/bluepy
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/thingy52.py -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/scanner.py -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/sensortag.py -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/uuids.json -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/blescan.py -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/bluepy-helper.c -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/bluepy-helper -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/get_services.py -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/bluez-src.tgz -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/version.h -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/scan_fuzz.py -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/__init__.py -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/Makefile -> build/bdist.linux-x86_64/egg/bluepy
copying build/lib/bluepy/btle.py -> build/bdist.linux-x86_64/egg/bluepy
byte-compiling build/bdist.linux-x86_64/egg/bluepy/thingy52.py to thingy52.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/bluepy/scanner.py to scanner.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/bluepy/sensortag.py to sensortag.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/bluepy/blescan.py to blescan.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/bluepy/get_services.py to get_services.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/bluepy/scan_fuzz.py to scan_fuzz.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/bluepy/__init__.py to __init__.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/bluepy/btle.py to btle.cpython-311.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying bluepy.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying bluepy.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying bluepy.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying bluepy.egg-info/entry_points.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying bluepy.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
bluepy.__pycache__.btle.cpython-311: module references __file__
creating dist
creating 'dist/bluepy-1.3.0-py3.11.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing bluepy-1.3.0-py3.11.egg
removing '/usr/local/lib/python3.11/dist-packages/bluepy-1.3.0-py3.11.egg' (and everything under it)
creating /usr/local/lib/python3.11/dist-packages/bluepy-1.3.0-py3.11.egg
Extracting bluepy-1.3.0-py3.11.egg to /usr/local/lib/python3.11/dist-packages
bluepy 1.3.0 is already the active version in easy-install.pth
Installing blescan script to /usr/local/bin
Installing sensortag script to /usr/local/bin
Installing thingy52 script to /usr/local/bin
Installed /usr/local/lib/python3.11/dist-packages/bluepy-1.3.0-py3.11.egg
Processing dependencies for bluepy==1.3.0
Finished processing dependencies for bluepy==1.3.0
Lecture des listes de paquets…
Construction de l'arbre des dépendances…
Lecture des informations d'état…
Le paquet « python3-cryptography » n'est pas installé, et ne peut donc être supprimé
Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires :
appstream distro-info-data libappstream4 libstemmer0d libxmlb2 packagekit
packagekit-tools python-apt-common python3-apt python3-blinker
python3-cffi-backend python3-distro python3-httplib2 python3-jwt
python3-lazr.uri python3-pyparsing python3-wadllib
Veuillez utiliser « sudo apt autoremove » pour les supprimer.
0 mis à jour, 0 nouvellement installés, 0 à enlever et 133 non mis à jour.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
********************************************************
*			 Installation terminée			

Informations Jeedom

Core : 4.5.2 (master)
DNS Jeedom : oui

Plugin : Bluetooth Advertisement
Version : 2024-09-05 01:00:47 (stable)
Statut Démon : Stoppé - (Inconnue)

Si quelqu’un a une solution
merci d’avance

Salut,

Ce qui pourrait nous mener vers cette solution c’est d’avoir la page santé de ton jeedom :wink:

Dsl j’ai essayé de mettre un maximun d’information , mais oublié celui la :slight_smile:

santé bluetooth :
|Dépendances|NOK|
|Configuration démon |NOK|
|Statut démon|NOK|

Dans d’autres posts de ce forum, je vois que blea n’a pas l’air totalement compatible debian 12 …
Il s’appuie visiblement sur une librairie trop ancienne.

Bonjour,

Comme indiqué dans le log, tu ne peux plus installer de paquet python sans passer par un venv. Et ce n’est pas ce que fait le plugin.
Les plugins récents mis à jour créent un tel environnement.

A priori d’après tes modules BT plugin-mqttdiscovery devrait permettre de remplacer avantageusement BLEA.

Bonjour,

Merci pour l’info , j’ai vu qu’il y avait aussi MQTT BLE Scanner
ca peut fonctionner aussi ou il faut impérativement le plugin mqttdiscovery?

Je ne connais pas l’autre plugin désolé.

Bonjour @Madcow ,
Juste en installant le plugin mqttdiscovery ca suffit a détecter les equipements bluetooth de ma clé asuz ou il y a d’autre manip à réaliser?
c’est pour savoir avant d’acheter le plugin voir si je ne pars pas dans quelque chose de trop compliqué :slight_smile:
merci d’avance

Bonjour,

En fait pour le BT le plugin MQTTDiscovery est lié à plugin-tgw (je simplifie il y a d’autres moyens existants ).
Pour un installation simplifiée il te faut donc les 2 plugins en BT.

2 « J'aime »