Home assistant update failing

Creating a bug report/issue

Required Information

  • DietPi version
    G_DIETPI_VERSION_CORE=8
    G_DIETPI_VERSION_SUB=21
    G_DIETPI_VERSION_RC=1
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’

  • Distro version
    bullseye 1

  • Kernel version
    Linux DietPi 4.14.58v7-aufs #1 SMP Sat Jul 28 20:40:59 CEST 2018 armv7l GNU/Linux

  • Architecture
    armhf

  • SBC model
    RPi 3 Model B (armv7l)

  • Power supply used | 5V 1A

  • SD card used | Samsung Ultra

Additional Information (if applicable)

  • Software title | Home Assistant
  • Was the software title installed freshly or updated/migrated?
    Yes
  • Can this issue be replicated on a fresh installation of DietPi?
    No idea
  • Bug report ID | 4c0e183f-c0b7-427f-87d5-027caeae0187

Steps to reproduce

  1. sudo -u homeassistant bash
  2. . /home/homeassistant/pyenv-activate.sh
  3. pip3 install --upgrade homeassistant

Expected behaviour

  • Hoping to update homeassistant to most recent version

Actual behaviour

  • Error while upgrading

Extra details


homeassistant@DietPi:/root$ . /home/homeassistant/pyenv-activate.sh
homeassistant@DietPi:~$ pip3 install --upgrade homeassistant
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: homeassistant in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (2022.12.8)
Collecting homeassistant
  Obtaining dependency information for homeassistant from https://files.pythonhosted.org/packages/b5/d7/baad7784c2749ce7c91f8ab2060d93be1b58de82c79545c6c24954ec4276/homeassistant-2023.7.3-py3-none-any.whl.metadata
  Using cached homeassistant-2023.7.3-py3-none-any.whl.metadata (3.8 kB)
Collecting aiohttp==3.8.5 (from homeassistant)
  Using cached aiohttp-3.8.5-cp310-cp310-linux_armv7l.whl
Requirement already satisfied: astral==2.2 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from homeassistant) (2.2)
Requirement already satisfied: async-timeout==4.0.2 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from homeassistant) (4.0.2)
Collecting attrs==22.2.0 (from homeassistant)
  Using cached https://www.piwheels.org/simple/attrs/attrs-22.2.0-py3-none-any.whl (60 kB)
Requirement already satisfied: atomicwrites-homeassistant==1.4.1 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from homeassistant) (1.4.1)
Requirement already satisfied: awesomeversion==22.9.0 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from homeassistant) (22.9.0)
Collecting bcrypt==4.0.1 (from homeassistant)
  Using cached bcrypt-4.0.1.tar.gz (25 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: certifi>=2021.5.30 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from homeassistant) (2022.12.7)
Collecting ciso8601==2.3.0 (from homeassistant)
  Using cached ciso8601-2.3.0.tar.gz (26 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting httpx==0.24.1 (from homeassistant)
  Using cached https://www.piwheels.org/simple/httpx/httpx-0.24.1-py3-none-any.whl (75 kB)
Collecting home-assistant-bluetooth==1.10.0 (from homeassistant)
  Using cached home_assistant_bluetooth-1.10.0.tar.gz (10 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting ifaddr==0.2.0 (from homeassistant)
  Using cached https://www.piwheels.org/simple/ifaddr/ifaddr-0.2.0-py3-none-any.whl (12 kB)
Requirement already satisfied: Jinja2==3.1.2 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from homeassistant) (3.1.2)
Collecting lru-dict==1.2.0 (from homeassistant)
  Using cached lru-dict-1.2.0.tar.gz (10 kB)
  Preparing metadata (setup.py) ... done
Collecting PyJWT==2.7.0 (from homeassistant)
  Using cached https://www.piwheels.org/simple/pyjwt/PyJWT-2.7.0-py3-none-any.whl (22 kB)
Collecting cryptography==41.0.1 (from homeassistant)
  Using cached cryptography-41.0.1.tar.gz (629 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting pyOpenSSL==23.2.0 (from homeassistant)
  Using cached https://www.piwheels.org/simple/pyopenssl/pyOpenSSL-23.2.0-py3-none-any.whl (59 kB)
Collecting orjson==3.9.1 (from homeassistant)
  Obtaining dependency information for orjson==3.9.1 from https://files.pythonhosted.org/packages/c5/09/836f32cc0a3c13e18ec3487957989387b60f9e7cfbe920773ad4b329db55/orjson-3.9.1-cp310-cp310-manylinux_2_17_armv7l.manylinux2014_armv7l.whl.metadata
  Using cached orjson-3.9.1-cp310-cp310-manylinux_2_17_armv7l.manylinux2014_armv7l.whl.metadata (49 kB)
Collecting pip<23.2,>=21.3.1 (from homeassistant)
  Using cached https://www.piwheels.org/simple/pip/pip-23.1.2-py3-none-any.whl (2.1 MB)
Requirement already satisfied: python-slugify==4.0.1 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from homeassistant) (4.0.1)
Collecting PyYAML==6.0.1 (from homeassistant)
  Using cached PyYAML-6.0.1.tar.gz (125 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting requests==2.31.0 (from homeassistant)
  Using cached https://www.piwheels.org/simple/requests/requests-2.31.0-py3-none-any.whl (62 kB)
Collecting typing-extensions<5.0,>=4.6.3 (from homeassistant)
  Using cached https://www.piwheels.org/simple/typing-extensions/typing_extensions-4.7.1-py3-none-any.whl (33 kB)
Collecting ulid-transform==0.7.2 (from homeassistant)
  Using cached ulid_transform-0.7.2.tar.gz (14 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: voluptuous==0.13.1 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from homeassistant) (0.13.1)
Collecting voluptuous-serialize==2.6.0 (from homeassistant)
  Using cached https://www.piwheels.org/simple/voluptuous-serialize/voluptuous_serialize-2.6.0-py3-none-any.whl (6.8 kB)
Collecting yarl==1.9.2 (from homeassistant)
  Using cached yarl-1.9.2.tar.gz (184 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: charset-normalizer<4.0,>=2.0 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from aiohttp==3.8.5->homeassistant) (2.1.1)
Requirement already satisfied: multidict<7.0,>=4.5 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from aiohttp==3.8.5->homeassistant) (6.0.4)
Requirement already satisfied: frozenlist>=1.1.1 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from aiohttp==3.8.5->homeassistant) (1.3.3)
Requirement already satisfied: aiosignal>=1.1.2 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from aiohttp==3.8.5->homeassistant) (1.3.1)
Requirement already satisfied: pytz in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from astral==2.2->homeassistant) (2022.7)
Requirement already satisfied: cffi>=1.12 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from cryptography==41.0.1->homeassistant) (1.15.1)
Requirement already satisfied: httpcore<0.18.0,>=0.15.0 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from httpx==0.24.1->homeassistant) (0.16.3)
Requirement already satisfied: idna in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from httpx==0.24.1->homeassistant) (3.4)
Requirement already satisfied: sniffio in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from httpx==0.24.1->homeassistant) (1.3.0)
Requirement already satisfied: MarkupSafe>=2.0 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from Jinja2==3.1.2->homeassistant) (2.1.1)
Requirement already satisfied: text-unidecode>=1.3 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from python-slugify==4.0.1->homeassistant) (1.3)
Requirement already satisfied: urllib3<3,>=1.21.1 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from requests==2.31.0->homeassistant) (1.26.13)
Requirement already satisfied: pycparser in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from cffi>=1.12->cryptography==41.0.1->homeassistant) (2.21)
Requirement already satisfied: h11<0.15,>=0.13 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from httpcore<0.18.0,>=0.15.0->httpx==0.24.1->homeassistant) (0.14.0)
Requirement already satisfied: anyio<5.0,>=3.0 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from httpcore<0.18.0,>=0.15.0->httpx==0.24.1->homeassistant) (3.6.2)
Using cached homeassistant-2023.7.3-py3-none-any.whl (27.4 MB)
Using cached orjson-3.9.1-cp310-cp310-manylinux_2_17_armv7l.manylinux2014_armv7l.whl (127 kB)
Building wheels for collected packages: bcrypt, ciso8601, cryptography, home-assistant-bluetooth, lru-dict, PyYAML, ulid-transform, yarl
  Building wheel for bcrypt (pyproject.toml) ... done
  Created wheel for bcrypt: filename=bcrypt-4.0.1-cp310-cp310-linux_armv7l.whl size=706360 sha256=f0a51f297b1e35335ce1e9cdb414a0fb6a299b8e95b9bf431e9951e63c1f2609
  Stored in directory: /home/homeassistant/.cache/pip/wheels/db/db/c4/5fec7451b1fb200056c9141abba8a7d48c8399e5fa69484090
  Building wheel for ciso8601 (pyproject.toml) ... done
  Created wheel for ciso8601: filename=ciso8601-2.3.0-cp310-cp310-linux_armv7l.whl size=36511 sha256=1af2eb3eefb3222d6bb15de55f93b487f775459537935562367b49569f5734ad
  Stored in directory: /home/homeassistant/.cache/pip/wheels/f3/43/b0/6e46d9fef6612806b09b4c43ade97c3a908bca242fa61cb402
  Building wheel for cryptography (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for cryptography (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [288 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.linux-armv7l-cpython-310
      creating build/lib.linux-armv7l-cpython-310/cryptography
      copying src/cryptography/utils.py -> build/lib.linux-armv7l-cpython-310/cryptography
      copying src/cryptography/fernet.py -> build/lib.linux-armv7l-cpython-310/cryptography
      copying src/cryptography/exceptions.py -> build/lib.linux-armv7l-cpython-310/cryptography
      copying src/cryptography/__init__.py -> build/lib.linux-armv7l-cpython-310/cryptography
      copying src/cryptography/__about__.py -> build/lib.linux-armv7l-cpython-310/cryptography
      creating build/lib.linux-armv7l-cpython-310/cryptography/x509
      copying src/cryptography/x509/oid.py -> build/lib.linux-armv7l-cpython-310/cryptography/x509
      copying src/cryptography/x509/ocsp.py -> build/lib.linux-armv7l-cpython-310/cryptography/x509
      copying src/cryptography/x509/name.py -> build/lib.linux-armv7l-cpython-310/cryptography/x509
      copying src/cryptography/x509/general_name.py -> build/lib.linux-armv7l-cpython-



           Running `/home/homeassistant/.rustup/toolchains/stable-armv7-unknown-linux-gnueabihf/bin/rustc --crate-name libc /home/homeassistant/.cargo/registry/src/index.crates.io-1cd66030c949c28d/libc-0.2.144/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C overflow-checks=on --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=59092c2a51e19812 -C extra-filename=-59092c2a51e19812 --out-dir /tmp/pip-install-fey0agji/cryptography_e942fbec1dcc4b4e96e7ab7bb008102a/src/rust/target/release/deps -L dependency=/tmp/pip-install-fey0agji/cryptography_e942fbec1dcc4b4e96e7ab7bb008102a/src/rust/target/release/deps --cap-lints allow --cfg freebsd11 --cfg libc_priv_mod_use --cfg libc_union --cfg libc_const_size_of --cfg libc_align --cfg libc_int128 --cfg libc_core_cvoid --cfg libc_packedN --cfg libc_cfg_target_vendor --cfg libc_non_exhaustive --cfg libc_long_array --cfg libc_ptr_addr_of --cfg libc_underscore_const_names --cfg libc_const_extern_fn`
           Running `/tmp/pip-install-fey0agji/cryptography_e942fbec1dcc4b4e96e7ab7bb008102a/src/rust/target/release/build/openssl-sys-c0be9edd519ea8ad/build-script-main`
           Running `/tmp/pip-install-fey0agji/cryptography_e942fbec1dcc4b4e96e7ab7bb008102a/src/rust/target/release/build/syn-7ff6606d95701e40/build-script-build`
      error: failed to run custom build command for `openssl-sys v0.9.88`

      Caused by:
        process didn't exit successfully: `/tmp/pip-install-fey0agji/cryptography_e942fbec1dcc4b4e96e7ab7bb008102a/src/rust/target/release/build/openssl-sys-c0be9edd519ea8ad/build-script-main` (exit status: 101)
        --- stdout
        cargo:rerun-if-env-changed=ARMV7_UNKNOWN_LINUX_GNUEABIHF_OPENSSL_LIB_DIR
        ARMV7_UNKNOWN_LINUX_GNUEABIHF_OPENSSL_LIB_DIR unset
        cargo:rerun-if-env-changed=OPENSSL_LIB_DIR
        OPENSSL_LIB_DIR unset
        cargo:rerun-if-env-changed=ARMV7_UNKNOWN_LINUX_GNUEABIHF_OPENSSL_INCLUDE_DIR
        ARMV7_UNKNOWN_LINUX_GNUEABIHF_OPENSSL_INCLUDE_DIR unset
        cargo:rerun-if-env-changed=OPENSSL_INCLUDE_DIR
        OPENSSL_INCLUDE_DIR unset
        cargo:rerun-if-env-changed=ARMV7_UNKNOWN_LINUX_GNUEABIHF_OPENSSL_DIR
        ARMV7_UNKNOWN_LINUX_GNUEABIHF_OPENSSL_DIR unset
        cargo:rerun-if-env-changed=OPENSSL_DIR
        OPENSSL_DIR unset
        cargo:rerun-if-env-changed=OPENSSL_NO_PKG_CONFIG
        cargo:rerun-if-env-changed=PKG_CONFIG_armv7-unknown-linux-gnueabihf
        cargo:rerun-if-env-changed=PKG_CONFIG_armv7_unknown_linux_gnueabihf
        cargo:rerun-if-env-changed=HOST_PKG_CONFIG
        cargo:rerun-if-env-changed=PKG_CONFIG
        cargo:rerun-if-env-changed=OPENSSL_STATIC
        cargo:rerun-if-env-changed=OPENSSL_DYNAMIC
        cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
        cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
        cargo:rerun-if-env-changed=PKG_CONFIG_PATH_armv7-unknown-linux-gnueabihf
        cargo:rerun-if-env-changed=PKG_CONFIG_PATH_armv7_unknown_linux_gnueabihf
        cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
        cargo:rerun-if-env-changed=PKG_CONFIG_PATH
        cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_armv7-unknown-linux-gnueabihf
        cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_armv7_unknown_linux_gnueabihf
        cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
        cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
        cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_armv7-unknown-linux-gnueabihf
        cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_armv7_unknown_linux_gnueabihf
        cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
        cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
        cargo:rerun-if-env-changed=OPENSSL_STATIC
        cargo:rerun-if-env-changed=OPENSSL_DYNAMIC
        cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
        cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
        cargo:rerun-if-env-changed=PKG_CONFIG_PATH_armv7-unknown-linux-gnueabihf
        cargo:rerun-if-env-changed=PKG_CONFIG_PATH_armv7_unknown_linux_gnueabihf
        cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
        cargo:rerun-if-env-changed=PKG_CONFIG_PATH
        cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_armv7-unknown-linux-gnueabihf
        cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_armv7_unknown_linux_gnueabihf
        cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
        cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
        cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_armv7-unknown-linux-gnueabihf
        cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_armv7_unknown_linux_gnueabihf
        cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
        cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
        run pkg_config fail: Could not run `PKG_CONFIG_ALLOW_SYSTEM_CFLAGS="1" "pkg-config" "--libs" "--cflags" "openssl"`
        The pkg-config command could not be found.

        Most likely, you need to install a pkg-config package for your OS.
        Try `apt install pkg-config`, or `yum install pkg-config`,
        or `pkg install pkg-config`, or `apk add pkgconfig` depending on your distribution.

        If you've already installed it, ensure the pkg-config command is one of the
        directories in the PATH environment variable.

        If you did not expect this build to link to a pre-installed system library,
        then check documentation of the openssl-sys crate for an option to
        build the library from source, or disable features or dependencies
        that require pkg-config.

        --- stderr
        thread 'main' panicked at '

        Could not find directory of OpenSSL installation, and this `-sys` crate cannot
        proceed without this knowledge. If OpenSSL is installed and this crate had
        trouble finding it,  you can set the `OPENSSL_DIR` environment variable for the
        compilation process.

        Make sure you also have the development packages of openssl installed.
        For example, `libssl-dev` on Ubuntu or `openssl-devel` on Fedora.

        If you're in a situation where you think the directory *should* be found
        automatically, please open a bug at https://github.com/sfackler/rust-openssl
        and include information about your system as well as this message.

        $HOST = armv7-unknown-linux-gnueabihf
        $TARGET = armv7-unknown-linux-gnueabihf
        openssl-sys = 0.9.88


        It looks like you're compiling on Linux and also targeting Linux. Currently this
        requires the `pkg-config` utility to find OpenSSL but unfortunately `pkg-config`
        could not be found. If you have OpenSSL installed you can likely fix this by
        installing `pkg-config`.

        ', /home/homeassistant/.cargo/registry/src/index.crates.io-1cd66030c949c28d/openssl-sys-0.9.88/build/find_normal.rs:190:5
        note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
      warning: build failed, waiting for other jobs to finish...

          =============================DEBUG ASSISTANCE=============================
          If you are seeing a compilation error please try the following steps to
          successfully install cryptography:
          1) Upgrade to the latest pip and try again. This will fix errors for most
             users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
          2) Read https://cryptography.io/en/latest/installation/ for specific
             instructions for your platform.
          3) Check our frequently asked questions for more information:
             https://cryptography.io/en/latest/faq/
          4) Ensure you have a recent Rust toolchain installed:
             https://cryptography.io/en/latest/installation/#rust

          Python: 3.10.9
          platform: Linux-4.14.58v7-aufs-armv7l-with-glibc2.31
          pip: n/a
          setuptools: 68.2.0
          setuptools_rust: 1.7.0
          rustc: n/a
          =============================DEBUG ASSISTANCE=============================

      error: `cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/rust/Cargo.toml --release -v --features pyo3/extension-module --crate-type cdylib --` failed with code 101
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for cryptography
  Building wheel for home-assistant-bluetooth (pyproject.toml) ... done
  Created wheel for home-assistant-bluetooth: filename=home_assistant_bluetooth-1.10.0-cp310-cp310-manylinux_2_31_armv7l.whl size=349596 sha256=5e76c2ba4466193e58f7529521095c0ffea6bbb992e98d4af55d40ca9b9911eb
  Stored in directory: /home/homeassistant/.cache/pip/wheels/1b/2f/d9/b672eb313abc43817a8408e51717c10be00c21f89034322981
  Building wheel for lru-dict (setup.py) ... done
  Created wheel for lru-dict: filename=lru_dict-1.2.0-cp310-cp310-linux_armv7l.whl size=26638 sha256=fc92d1f9dd46e360c82ff344eca7a629966a0fb4cf6fe21e4d309d013dbae4eb
  Stored in directory: /home/homeassistant/.cache/pip/wheels/b8/c2/b8/12ffc3dc79cb0f01297342f16e2e92c444dc917fba910c0b36
  Building wheel for PyYAML (pyproject.toml) ... done
  Created wheel for PyYAML: filename=PyYAML-6.0.1-cp310-cp310-linux_armv7l.whl size=45361 sha256=34849fe8c73b69f8858d603b206c8b17a702091eea667ad45b76e0240e99d8aa
  Stored in directory: /home/homeassistant/.cache/pip/wheels/31/d1/78/088142cfc0422adcca7bb0af40ef696b55b777a44f2e10739c
  Building wheel for ulid-transform (pyproject.toml) ... done
  Created wheel for ulid-transform: filename=ulid_transform-0.7.2-cp310-cp310-manylinux_2_31_armv7l.whl size=222321 sha256=693364f4c2b78b8d8d177addc2128c60581bc8f31382f5e71555776bd84a5018
  Stored in directory: /home/homeassistant/.cache/pip/wheels/c0/95/c7/39f166649f37bd4f89b04c1abd7bf077ace25c89f4039520e4
  Building wheel for yarl (pyproject.toml) ... done
  Created wheel for yarl: filename=yarl-1.9.2-cp310-cp310-linux_armv7l.whl size=253171 sha256=c8a578ea4aa1d416f7c931c28394327721c8249347b3d7729acfb8b3823379e3
  Stored in directory: /home/homeassistant/.cache/pip/wheels/66/b6/b8/1a4ac9b4227cd4212504cc12bf9147c30534b8d5416233fc92
Successfully built bcrypt ciso8601 home-assistant-bluetooth lru-dict PyYAML ulid-transform yarl
Failed to build cryptography
ERROR: Could not build wheels for cryptography, which is required to install pyproject.toml-based projects
homeassistant@DietPi:~$
homeassistant@DietPi:~$
homeassistant@DietPi:~$


Hm there were some similiar issues:
https://dietpi.com/forum/t/unable-to-upgrade-home-assistant-to-2021-10-x/5823/7
https://dietpi.com/forum/t/homeassistant-fail-to-start-after-update/15104/5

maybe you can find a solution there

Hi Jappe, I have tried steps from POST#2 last time as well. It went well and tried upgrading homeassistant same issues.
Here’s my current output of cryptography install

homeassistant@DietPi:~$ curl -sSfL 'https://sh.rustup.rs' -o rustup-init.sh
homeassistant@DietPi:~$ chmod +x rustup-init.sh
homeassistant@DietPi:~$ ./rustup-init.sh -y --profile minimal
info: downloading installer
info: profile set to 'minimal'
info: default host triple is armv7-unknown-linux-gnueabihf
warning: Updating existing toolchain, profile choice will be ignored
info: syncing channel updates for 'stable-armv7-unknown-linux-gnueabihf'
info: default toolchain set to 'stable-armv7-unknown-linux-gnueabihf'

  stable-armv7-unknown-linux-gnueabihf unchanged - rustc 1.72.0 (5680fa18f 2023-08-23)


Rust is installed now. Great!

To get started you may need to restart your current shell.
This would reload your PATH environment variable to include
Cargo's bin directory ($HOME/.cargo/bin).

To configure your current shell, run:
source "$HOME/.cargo/env"
homeassistant@DietPi:~$ source "$HOME/.cargo/env"
homeassistant@DietPi:~$ pip3 install cryptography
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: cryptography in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (38.0.3)
Requirement already satisfied: cffi>=1.12 in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from cryptography) (1.15.1)
Requirement already satisfied: pycparser in ./.pyenv/versions/3.10.9/lib/python3.10/site-packages (from cffi>=1.12->cryptography) (2.21)

I am rerunning the uprade again to see if anything changes.

Issue still persists :frowning:

      error: `cargo rustc --lib --message-format=json-render-diagnostics --manifest-path src/rust/Cargo.toml --release -v --features pyo3/extension-module --crate-type cdylib --` failed with code 101
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for cryptography
Failed to build cryptography
ERROR: Could not build wheels for cryptography, which is required to install pyproject.toml-based projects

The issue might be similar to an older one but probably different.

Before we are going to investigate further, do you know why your kernel version is that old??

On Raspberry Pi, it should be 6.1.21 already. Can you share following?

apt update
apt upgrade

That didn’t help for updating kernel. I ran it multiple times just to make sure. It’s still the same. Here’s the out from above commands.

root@DietPi:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@DietPi:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@DietPi:~# uname -a
Linux DietPi 4.14.58v7-aufs #1 SMP Sat Jul 28 20:40:59 CEST 2018 armv7l GNU/Linux
root@DietPi:~#

you missed to share output of

apt update

Here it is,

root@DietPi:~# apt update
Get:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15.0 kB]
Hit:2 https://archive.raspberrypi.org/debian bullseye InRelease
Fetched 15.0 kB in 1s (10.0 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
root@DietPi:~#

Can you share your source file configuration

for i in /etc/apt/sources.list{,.d/*.list}; do echo "$i:"; cat "$i"; done

Here it is,

root@DietPi:~# for i in /etc/apt/sources.list{,.d/*.list}; do echo "$i:"; cat "$i"; done
/etc/apt/sources.list:
deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free
/etc/apt/sources.list.d/docker.list:
deb https://download.docker.com/linux/raspbian/ bullseye stable
/etc/apt/sources.list.d/raspi.list:
deb https://archive.raspberrypi.org/debian/ bullseye main
root@DietPi:~#

that is fine. Did you already reboot your system? Does it still show old kernel?

uname -a

If yes, can you check if there are preferences configured.

ls -la /etc/apt /etc/apt/preferences.d/

Yes, multiple reboots as I am having another issue (separate one, not able to install portainer, thinking of moving Homeassistant from python install to docker one)

root@DietPi:~# uname -a
Linux DietPi 4.14.58v7-aufs #1 SMP Sat Jul 28 20:40:59 CEST 2018 armv7l GNU/Linux
r


root@DietPi:~# ls -la /etc/apt /etc/apt/preferences.d/
/etc/apt:
total 24
drwxr-xr-x  10 root root 4096 Sep 10 10:51 .
drwxr-xr-x 122 root root 4096 Sep 10 11:47 ..
drwxr-xr-x   2 root root 4096 Aug 26 19:42 apt.conf.d
drwxr-xr-x   2 root root    3 Jun 10  2021 auth.conf.d
drwxr-xr-x   2 root root    3 Jun 10  2021 preferences.d
-rw-r--r--   1 root root   77 May 29  2022 sources.list
drwxr-xr-x   2 root root 4096 Sep 10 10:51 sources.list.d
drwxr-xr-x   2 root root 4096 Sep 10 10:51 trusted.gpg.d

/etc/apt/preferences.d/:
total 4
drwxr-xr-x  2 root root    3 Jun 10  2021 .
drwxr-xr-x 10 root root 4096 Sep 10 10:51 ..
root@DietPi:~#

Sorry for late response but I was sick the last days.

Basically Docker issues are related to the old kernel version and we need to find our why it is not updated. Once this is solved, we could check HA afterwards.

@MichaIng any ideas why kernel stays on that old version 4.14.58 and is not updated to 6.1?

Do you think berryboot setup has anything to do with it?

This is super important information. Of course, it changes the whole issue around your kernel. Best to my knowledge Berryboot has an own kernel that can’t be updated on regular ways Berryboot | Portainer installation problems · Issue #4943 · MichaIng/DietPi · GitHub

If possible stay away from Berryboot.


as we can’t change the kernel, can you try to reinstall HA and post the whole/entire log pls.

So sorry on not providing the complete info. I didn’t know the underlying architecture of the system. So you want me to reinstall HA with current (berryboot) setup? Or prepare new setup all together?

try following on your current system to reinstall HA

dietpi-software reinstall 157

On the subject of the kernel, you must be clear whether you want to stay with the old, restricted kernel or whether you want an update. In the case of an update, you would have to install a new system without berryboot.

Reinstall is failing with following message

root@DietPi:~# dietpi-software reinstall 157
[  OK  ] DietPi-Software | Initialised database
[  OK  ] DietPi-Software | Reading database

 DietPi-Software
─────────────────────────────────────────────────────
 Mode: Automated reinstall

[FAILED] DietPi-Software | Software title (Home Assistant) is not supported on Debian Bullseye.
root@DietPi:~#

Is there any more recent version of dietpi which is berryboot compatible? I am using my current one with retropie for kids gaming console.

This has nothing to do with DietPi and nothing we can change from our side. It’s simply the way how Berryboot is working. Using Berryboot, the topic with the kernel is working as disgned by Berryboot.

Ahh yeah we disabled HA on everything below Debian Bookworm because ha-av requires FFmpeg headers >=4.4


What is the output if you try to update manually?

sudo -u homeassistant bash
. /home/homeassistant/pyenv-activate.sh
pip3 install --upgrade homeassistant

Another way you could think of, to upgrade your system to Debian Bookworm Debian Bookworm has been released – DietPi Blog But this will not change anything on the kernel version.

However, do a backup before.

Sadly this how it was started at the beginning. :frowning: