[jannisf@t480s ~]$ vorta
Traceback (most recent call last):
File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 563, in from_name
return next(cls.discover(name=name))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
StopIteration
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/vorta", line 33, in <module>
sys.exit(load_entry_point('vorta==0.8.12', 'gui_scripts', 'vorta')())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/bin/vorta", line 22, in importlib_load_entry_point
for entry_point in distribution(dist_name).entry_points
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 981, in distribution
return Distribution.from_name(distribution_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 565, in from_name
raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for vorta
A reinstallation of vorta fixed it.
Must happened because of a python package update.
Some packages still tried to use a old python version.
See pacman -Qoq /usr/lib/python3.10
It is an AUR package, it’s source is in ~/.cache/yay/, in the vorta directory it has already built some packages against python3.10, it does not “recognise” this as a problem, the problem is that we now are on python 3.11 and all the libs are in a new directory tree.
It will only rebuild everything on a cleanBuild, so it fails because it cannot find all the correct paths and resources it needs.