My backups broke again with this error:
DEBUG: sys.path=['/usr/bin', '/usr/lib/python310.zip', '/usr/lib/python3.10', '/usr/lib/python3.10/lib-dynload', '/usr/local/lib/python3.10/dist-packages', '/usr/lib/python3/dist-packages']
DEBUG: sys.executable=/usr/bin/python3
DEBUG: os.environ['PYTHONPATH']=None
Traceback (most recent call last):
File "/usr/bin/duplicity", line 5, in <module>
from duplicity.__main__ import dup_run
File "/usr/lib/python3/dist-packages/duplicity/__main__.py", line 39, in <module>
from duplicity import tempdir
File "/usr/lib/python3/dist-packages/duplicity/tempdir.py", line 35, in <module>
from duplicity import config
File "/usr/lib/python3/dist-packages/duplicity/config.py", line 32, in <module>
from duplicity import gpg
File "/usr/lib/python3/dist-packages/duplicity/gpg.py", line 35, in <module>
import gnupg
ModuleNotFoundError: No module named 'gnupg'
Something is wrong with the backup:
Anything long term problematic about using this fix below for duplicity rather than holding or reverting duplicity version? Or is this error different than what everyone was fixing in the thread above.