Home Assistant Update failed with -> pushd: Python-3.10.11: No such file or directory

Troubleshooting
1

Details:

  • Date | Sun Apr 9 19:55:59 CEST 2023
  • DietPi version | v8.16.2 (MichaIng/master)
  • Image creator |
  • Pre-image |
  • Hardware | RPi 4 Model B (aarch64) (ID=4)
  • Kernel version | Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
  • Distro | bullseye (ID=6,RASPBIAN=0)
  • Command | sudo -u homeassistant dash -c . /home/homeassistant/pyenv-activate.sh pyenv install 3.10.11 pyenv local 3.10.11 pip3 install -U pip setuptools wheel [ -z '' ] || pip3 install exec pip3 install homeassistant
  • Exit code | 127
  • Software title | DietPi-Software

Steps to reproduce:

  1. dietpi-software reinstall 157

Expected behaviour:

  • An successful Update of HA

Actual behaviour:

  • An Error Occurred

Extra details:

  • …

Additional logs:

Downloading Python-3.10.11.tar.xz...
-> https://www.python.org/ftp/python/3.10.11/Python-3.10.11.tar.xz
/home/homeassistant/.pyenv/plugins/python-build/bin/python-build: line 248: pushd: Python-3.10.11: No such file or directory

BUILD FAILED (Debian GNU/Linux 11 using python-build 20180424)

Inspect or clean up the working tree at /tmp/python-build.20230409195553.11028
Results logged to /tmp/python-build.20230409195553.11028.log

Last 10 log lines:
/tmp/python-build.20230409195553.11028 ~
warning: xz not found; consider installing `xz` package
tar (child): xz: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
pyenv: version `3.10.11' not installed
dash: 5: pip3: not found
dash: 7: exec: pip3: not found
2

You could try to install xz-utils.

3

Have a look at Home Assistant Install Fail · Issue #6297 · MichaIng/DietPi · GitHub

Looks like something changed on pip install.

4

Thanks Guy’s. It works now :slight_smile:

5

That such upstream changes need to happen the day after our release :smile:. Good that the solution is simple.

6

It was a pyenv bug solved upstream: pyenv/pyenv@7770894