vej, it affects me as well, using 34.3-1
Attaching the log.
In there one can see:
DUPLICITY: ERROR 19 DUPLICITY: . home/porridge/.cache/deja-dup/metadata not found in archive - no files restored.
And once I think about it, it makes sense, since /home is a symlink to /srv/home, and the metadata directory is there under the canonical path:
porridge@backup-server$ duplicity list-current-files file://`pwd`|grep cache/deja-dup GnuPG passphrase for decryption: Thu Mar 1 17:16:19 2018 srv/home/porridge/.cache/deja-dup Thu Mar 1 17:16:19 2018 srv/home/porridge/.cache/deja-dup/metadata Thu Mar 1 17:16:19 2018 srv/home/porridge/.cache/deja-dup/metadata/README porridge@backup-server$
How can I work around this?
vej, it affects me as well, using 34.3-1
Attaching the log.
In there one can see:
DUPLICITY: ERROR 19 .cache/ deja-dup/ metadata not found in archive - no files restored.
DUPLICITY: . home/porridge/
And once I think about it, it makes sense, since /home is a symlink to /srv/home, and the metadata directory is there under the canonical path:
porridge@ backup- server$ duplicity list-current-files file://`pwd`|grep cache/deja-dup porridge/ .cache/ deja-dup porridge/ .cache/ deja-dup/ metadata porridge/ .cache/ deja-dup/ metadata/ README backup- server$
GnuPG passphrase for decryption:
Thu Mar 1 17:16:19 2018 srv/home/
Thu Mar 1 17:16:19 2018 srv/home/
Thu Mar 1 17:16:19 2018 srv/home/
porridge@
How can I work around this?