Error while updating

INFO       Starting update for brewblox edge...
INFO       Updating brewblox-ctl...
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: pip in ./.venv/lib/python3.7/site-packages (23.1)
Collecting pip
  Downloading https://www.piwheels.org/simple/pip/pip-24.0-py3-none-any.whl (2.1                                                                                                                                                              MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 2.8 MB/s eta 0:00:00
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 23.1
    Uninstalling pip-23.1:
      Successfully uninstalled pip-23.1
Successfully installed pip-24.0
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Processing ./brewblox-ctl.tar.gz
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting click<9.0.0,>=8.1.7 (from brewblox-ctl==1.0.0)
  Downloading https://www.piwheels.org/simple/click/click-8.1.7-py3-none-any.whl (97 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 97.9/97.9 kB 956.4 kB/s eta 0:00:00
Requirement already satisfied: configobj<6.0.0,>=5.0.6 in ./.venv/lib/python3.7/site-packages (from brewblox-ctl==1.0.0) (5.0.6)
Collecting jinja2<4.0.0,>=3.1.3 (from brewblox-ctl==1.0.0)
  Downloading https://www.piwheels.org/simple/jinja2/jinja2-3.1.4-py3-none-any.whl (133 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 133.3/133.3 kB 1.8 MB/s eta 0:00:00
Requirement already satisfied: packaging<24.0,>=23.0 in ./.venv/lib/python3.7/site-packages (from brewblox-ctl==1.0.0) (23.0)
Collecting passlib<2.0.0,>=1.7.4 (from brewblox-ctl==1.0.0)
  Downloading https://www.piwheels.org/simple/passlib/passlib-1.7.4-py2.py3-none-any.whl (525 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 525.6/525.6 kB 2.5 MB/s eta 0:00:00
Requirement already satisfied: psutil<6.0.0,>=5.9.4 in ./.venv/lib/python3.7/site-packages (from brewblox-ctl==1.0.0) (5.9.4)
INFO: pip is looking at multiple versions of brewblox-ctl to determine which version is compatible with other requirements. This could take a while.
ERROR: Ignored the following yanked versions: 1.10.3
ERROR: Ignored the following versions that require a different python version: 2.6.0 Requires-Python >=3.8; 2.6.0b1 Requires-Python >=3.8; 2.6.1 Requires-Python >=3.8; 2.6.2 Requires-Python >=3.8; 2.6.3 Requires-Python >=3.8; 2.6.4 Requires-Python >=3.8; 2.7.0 Requires-Python >=3.8; 2.7.0b1 Requires-Python >=3.8; 2.7.1 Requires-Python >=3.8; 2.7.2 Requires-Python >=3.8; 2.7.3 Requires-Python >=3.8; 2.7.4 Requires-Python >=3.8; 2.8.0 Requires-Python >=3.8; 2.8.0b1 Requires-Python >=3.8; 2.8.1 Requires-Python >=3.8; 2.8.2 Requires-Python >=3.8
ERROR: Could not find a version that satisfies the requirement pydantic<3.0.0,>=2.6.4 (from brewblox-ctl) (from versions: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.1, 0.2, 0.2.1, 0.3, 0.4, 0.5, 0.6, 0.6.1, 0.6.2, 0.6.3, 0.6.4, 0.7, 0.7.1, 0.8, 0.9, 0.9.1, 0.10, 0.11, 0.11.1, 0.11.2, 0.12, 0.12.1, 0.13, 0.13.1, 0.14, 0.15, 0.16, 0.16.1, 0.17, 0.18, 0.18.1, 0.18.2, 0.19, 0.20a1, 0.20, 0.20.1, 0.21, 0.22, 0.23, 0.24, 0.25, 0.26, 0.27a1, 0.27, 0.28, 0.29, 0.30, 0.30.1, 0.31, 0.31.1, 0.32, 0.32.1, 0.32.2, 1.0b1, 1.0b2, 1.0, 1.1, 1.1.1, 1.2, 1.3, 1.4, 1.5, 1.5.1, 1.6, 1.6.1, 1.6.2, 1.7, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.8, 1.8.1, 1.8.2, 1.9.0a1, 1.9.0a2, 1.9.0, 1.9.1, 1.9.2, 1.10.0a1, 1.10.0a2, 1.10.0b1, 1.10.0, 1.10.1, 1.10.2, 1.10.4, 1.10.5, 1.10.6, 1.10.7, 1.10.8, 1.10.9, 1.10.10, 1.10.11, 1.10.12, 1.10.13, 1.10.14, 1.10.15, 1.10.16, 1.10.17, 2.0a1, 2.0a2, 2.0a3, 2.0a4, 2.0b1, 2.0b2, 2.0b3, 2.0, 2.0.1, 2.0.2, 2.0.3, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.3.0, 2.4.0, 2.4.1, 2.4.2, 2.5.0b1, 2.5.0, 2.5.1, 2.5.2, 2.5.3)
ERROR: No matching distribution found for pydantic<3.0.0,>=2.6.4
Command 'python3 -m pip install --prefer-binary ./brewblox-ctl.tar.gz' returned non-zero exit status 1.

Found a possible solution, right here.
Taking a snapshot first.

Which version of Raspbian are you running? I think it is probably very old and a fresh install of the latest version, then restoring a snapshot is best.