I got the patch applied without errors, however, running tox regression
tests yields the attached errors. mostly in restart it looks like. You can
run tox from the base directory with:
On Thu, May 7, 2015 at 6:02 AM, jitao <email address hidden> wrote:
> This patch base on repo from github
> repo: https://github.com/henrysher/duplicity
> commitid: 208987192288d0815455707c416735783c3ae42a
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1044715
>
> Title:
> Provide a file history feature
>
> Status in Duplicity - Bandwidth Efficient Encrypted Backup:
> New
>
> Bug description:
> Duplicity seems to be lacking to possibility to get a history of a
> file (changes dates) wrt backed-up versions of the file.
>
> It seems the only solution is to iterate list-current-files with
> different dates, which is very much inconvenient.
>
> Whereas duplicity may be fine to restore a full content of a recent
> backup, it is less useful to restore an ancient version of a file
> which has been modified several times in subsequent backups.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1044715/+subscriptions
>
I got the patch applied without errors, however, running tox regression
tests yields the attached errors. mostly in restart it looks like. You can
run tox from the base directory with:
$ /usr/bin/python -u /usr/local/bin/tox -r -e py27
...Thanks,
...Ken
On Thu, May 7, 2015 at 6:02 AM, jitao <email address hidden> wrote:
> This patch base on repo from github /github. com/henrysher/ duplicity 15455707c416735 783c3ae42a /bugs.launchpad .net/bugs/ 1044715 /bugs.launchpad .net/duplicity/ +bug/1044715/ +subscriptions
> repo: https:/
> commitid: 208987192288d08
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https:/
>
> Title:
> Provide a file history feature
>
> Status in Duplicity - Bandwidth Efficient Encrypted Backup:
> New
>
> Bug description:
> Duplicity seems to be lacking to possibility to get a history of a
> file (changes dates) wrt backed-up versions of the file.
>
> It seems the only solution is to iterate list-current-files with
> different dates, which is very much inconvenient.
>
> Whereas duplicity may be fine to restore a full content of a recent
> backup, it is less useful to restore an ancient version of a file
> which has been modified several times in subsequent backups.
>
> To manage notifications about this bug go to:
> https:/
>