0.6.21 is at least 3 years old and has been superseded.
On Wed, Jun 1, 2016 at 3:46 AM, Leon Arundell <email address hidden>
wrote:
> Please upgrade the status of this bug to "High."
>
> It has occurred several times on my Ubuntu 14.04 system in the past two
> months, and means that I cannot reliably use Duplicity to do incremental
> backups. The main alternatives seem to only offer time- and space-
> consuming complete backups.
>
> --
> You received this bug notification because you are subscribed to
> duplicity in 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"
>
> Status in Déjà Dup:
> Confirmed
> Status in duplicity package in Ubuntu:
> New
>
> Bug description:
> Linux release: Ubuntu 13.04 64bit
> Kernel: 3.8.0-29-generic
> Python: 2.7.4
> Deja Dup: 26.0
> Duplicity: 0.6.21
>
> Hi. I've tried to do my monthly or so backup recently, but Deja Dup
> crashed after trying to backup a very large file (VM disk with Windows
> 7, 50GB or so). I tried to do another one, this time excluding all my
> large VM's. However, now when trying to do a backup I'm getting the
> following error a few seconds after inputting my encryption password:
>
> Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
> in backup
>
> I've tried reinstalling both deja-dup and duplicity, purging
> duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
> deleting the backup files on the external drive, deleting it's config
> as described here http://askubuntu.com/questions/53980/how-to-delete-
> all-the-settings-for-deja-dup. I know (well, I have some evidence
> supporting this) that the drive itself isn't faulty as I managed to
> backup my old laptop to the drive using duplicity and it worked fine
> (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
> momentarily.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions
>
Go here <https:/ /launchpad. net/~duplicity- team/+archive/ ubuntu/ ppa> and add
the repository to your list. apt-get update / upgrade will bring in the
latest version which is a lot newer than the one you have.
0.6.21 is at least 3 years old and has been superseded.
On Wed, Jun 1, 2016 at 3:46 AM, Leon Arundell <email address hidden>
wrote:
> Please upgrade the status of this bug to "High." /bugs.launchpad .net/bugs/ 1217959 deja-dup/ metadata’ : File not found in backup" tom/.cache/ deja-dup/ metadata’ : File not found askubuntu. com/questions/ 53980/how- to-delete- settings- for-deja- dup. I know (well, I have some evidence /bugs.launchpad .net/deja- dup/+bug/ 1217959/ +subscriptions
>
> It has occurred several times on my Ubuntu 14.04 system in the past two
> months, and means that I cannot reliably use Duplicity to do incremental
> backups. The main alternatives seem to only offer time- and space-
> consuming complete backups.
>
> --
> You received this bug notification because you are subscribed to
> duplicity in Ubuntu.
> https:/
>
> Title:
> 'metadata' file not found when creating backup ("Could not restore
> ‘/home/user /.cache/
>
> Status in Déjà Dup:
> Confirmed
> Status in duplicity package in Ubuntu:
> New
>
> Bug description:
> Linux release: Ubuntu 13.04 64bit
> Kernel: 3.8.0-29-generic
> Python: 2.7.4
> Deja Dup: 26.0
> Duplicity: 0.6.21
>
> Hi. I've tried to do my monthly or so backup recently, but Deja Dup
> crashed after trying to backup a very large file (VM disk with Windows
> 7, 50GB or so). I tried to do another one, this time excluding all my
> large VM's. However, now when trying to do a backup I'm getting the
> following error a few seconds after inputting my encryption password:
>
> Could not restore ‘/home/
> in backup
>
> I've tried reinstalling both deja-dup and duplicity, purging
> duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
> deleting the backup files on the external drive, deleting it's config
> as described here http://
> all-the-
> supporting this) that the drive itself isn't faulty as I managed to
> backup my old laptop to the drive using duplicity and it worked fine
> (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
> momentarily.
>
> To manage notifications about this bug go to:
> https:/
>