je viens de passer du raspberry vers une machine virtuel (debian 11 64 bits ) sous proxmox .
blea me sort ce message : Attention je pense qu’il y a un soucis avec le démon que j’ai relancé plus de 3 fois consécutivement :
voici le log:
********************************************************
* Installation des dépendances *
********************************************************
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://phoscon.de/apt/deconz bullseye InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
libatlas-base-dev is already the newest version (3.10.3-10).
bluetooth is already the newest version (5.55-3.1).
libbluetooth-dev is already the newest version (5.55-3.1).
build-essential is already the newest version (12.9).
libffi-dev is already the newest version (3.3-6).
libopenjp2-7 is already the newest version (2.4.0-3).
python3-serial is already the newest version (3.5~b0-1).
python3-dev is already the newest version (3.9.2-3).
python3-pyudev is already the newest version (0.22.0-2).
python3-requests is already the newest version (2.25.1+dfsg-2).
python3-setuptools is already the newest version (52.0.0-4).
rfkill is already the newest version (2.36.1-8+deb11u1).
libssl-dev is already the newest version (1.1.1n-0+deb11u4).
libtiff5 is already the newest version (4.2.0-1+deb11u4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/1512 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 73103 files and directories currently installed.)
Preparing to unpack .../bluez_5.55-3.1_amd64.deb ...
Unpacking bluez (5.55-3.1) over (5.55-3.1) ...
Preparing to unpack .../python3_3.9.2-3_amd64.deb ...
running python pre-rtupdate hooks for python3.9...
Unpacking python3 (3.9.2-3) over (3.9.2-3) ...
Preparing to unpack .../python3-pip_20.3.4-4+deb11u1_all.deb ...
Unpacking python3-pip (20.3.4-4+deb11u1) over (20.3.4-4+deb11u1) ...
Setting up python3 (3.9.2-3) ...
running python rtupdate hooks for python3.9...
running python post-rtupdate hooks for python3.9...
Setting up bluez (5.55-3.1) ...
Setting up python3-pip (20.3.4-4+deb11u1) ...
Processing triggers for dbus (1.12.24-0+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...
Requirement already satisfied: setuptools in /usr/local/lib/python3.9/dist-packages (67.5.1)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Reading package lists...
Building dependency tree...
Reading state information...
libglib2.0-dev is already the newest version (2.66.8-1).
git is already the newest version (1:2.30.2-1+deb11u2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Requirement already satisfied: pyudev in /usr/local/lib/python3.9/dist-packages (0.24.0)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: pyserial in /usr/local/lib/python3.9/dist-packages (3.5)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: requests in /usr/local/lib/python3.9/dist-packages (2.21.0)
Requirement already satisfied: idna<2.9,>=2.5 in /usr/local/lib/python3.9/dist-packages (from requests) (2.8)
Requirement already satisfied: urllib3<1.25,>=1.21.1 in /usr/local/lib/python3.9/dist-packages (from requests) (1.24.3)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.9/dist-packages (from requests) (3.0.4)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.9/dist-packages (from requests) (2022.12.7)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: pybluez in /usr/local/lib/python3.9/dist-packages (0.22)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: pillow in /usr/local/lib/python3.9/dist-packages (9.4.0)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: numpy in /usr/local/lib/python3.9/dist-packages (1.24.2)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: bluepy in /usr/local/lib/python3.9/dist-packages (1.3.0)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Cloning into 'bluepy'...
/usr/local/lib/python3.9/dist-packages/setuptools/dist.py:788: 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
creating build
creating build/lib
creating build/lib/bluepy
copying bluepy/blescan.py -> build/lib/bluepy
copying bluepy/get_services.py -> build/lib/bluepy
copying bluepy/scanner.py -> build/lib/bluepy
copying bluepy/__init__.py -> build/lib/bluepy
copying bluepy/sensortag.py -> build/lib/bluepy
copying bluepy/btle.py -> build/lib/bluepy
copying bluepy/scan_fuzz.py -> build/lib/bluepy
copying bluepy/thingy52.py -> 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/Makefile -> build/lib/bluepy
/usr/local/lib/python3.9/dist-packages/setuptools/dist.py:788: 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/local/lib/python3.9/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
Working dir is /tmp/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
running build
running build_py
copying bluepy/bluepy-helper -> build/lib/bluepy
running install_lib
copying build/lib/bluepy/blescan.py -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/Makefile -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/get_services.py -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/scanner.py -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/__init__.py -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/bluepy-helper.c -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/sensortag.py -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/btle.py -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/bluepy-helper -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/uuids.json -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/scan_fuzz.py -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/thingy52.py -> /usr/lib/python3.9/site-packages/bluepy
copying build/lib/bluepy/bluez-src.tgz -> /usr/lib/python3.9/site-packages/bluepy
byte-compiling /usr/lib/python3.9/site-packages/bluepy/blescan.py to blescan.cpython-39.pyc
byte-compiling /usr/lib/python3.9/site-packages/bluepy/get_services.py to get_services.cpython-39.pyc
byte-compiling /usr/lib/python3.9/site-packages/bluepy/scanner.py to scanner.cpython-39.pyc
byte-compiling /usr/lib/python3.9/site-packages/bluepy/__init__.py to __init__.cpython-39.pyc
byte-compiling /usr/lib/python3.9/site-packages/bluepy/sensortag.py to sensortag.cpython-39.pyc
byte-compiling /usr/lib/python3.9/site-packages/bluepy/btle.py to btle.cpython-39.pyc
byte-compiling /usr/lib/python3.9/site-packages/bluepy/scan_fuzz.py to scan_fuzz.cpython-39.pyc
byte-compiling /usr/lib/python3.9/site-packages/bluepy/thingy52.py to thingy52.cpython-39.pyc
running install_egg_info
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'
removing '/usr/lib/python3.9/site-packages/bluepy-1.1.4-py3.9.egg-info' (and everything under it)
Copying bluepy.egg-info to /usr/lib/python3.9/site-packages/bluepy-1.1.4-py3.9.egg-info
running install_scripts
Installing blescan script to /usr/bin
Installing sensortag script to /usr/bin
Installing thingy52 script to /usr/bin
Requirement already satisfied: cryptography in /usr/local/lib/python3.9/dist-packages (39.0.2)
Requirement already satisfied: cffi>=1.12 in /usr/local/lib/python3.9/dist-packages (from cryptography) (1.15.1)
Requirement already satisfied: pycparser in /usr/local/lib/python3.9/dist-packages (from cffi>=1.12->cryptography) (2.21)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: pycrypto in /usr/local/lib/python3.9/dist-packages (2.6.1)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
********************************************************
* Installation terminée *
********************************************************
merci de vouloir bien m’aider