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? ** Attachment added: "deja-dup.log" https://bugs.launchpad.net/deja-dup/+bug/1217959/+attachment/5066388/+files/deja-dup.log ** Changed in: deja-dup Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217959 Title: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup" To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
