Provide a file history feature

Btw, this has already been discussed on the ML, for instance in : http://lists.nongnu.org/archive/html/duplicity-talk/2012-01/msg00001.html

This is a patch supported the feature.

$duplicity collection-status --file-changed c1 --archive-dir=./b/sigs file://./b
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Thu May 7 17:25:01 2015
-------------------------
File path: c1
Total number of backup: 4
 Type of backup set: Time:
                Full Thu May 7 17:25:01 2015
         Incremental Thu May 7 17:25:16 2015
         Incremental Thu May 7 17:25:24 2015
         Incremental Thu May 7 17:25:27 2015
-------------------------

This patch base on repo from github
repo: https://github.com/henrysher/duplicity
commitid: 208987192288d0815455707c416735783c3ae42a

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
> 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
>

Thanks for your reply.

I fixed them, and add 'Type of file change' col

However, there are 2 testcase about test_fiinal failed. These testcase also failed in bzr repo, I don't konw why

--Tao

Sorry, above patch has some debug code

Thanks for the quick fix. I'll get it merged in.

On Fri, May 8, 2015 at 2:58 AM, jitao <email address hidden> wrote:

> Sorry, above patch has some debug code
>
> ** Patch added: "support_single_file_history.patch"
>
> https://bugs.launchpad.net/duplicity/+bug/1044715/+attachment/4393437/+files/support_single_file_history.patch
>
> --
> 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
>

The feature fix provided took way too much memory to process and caused failures when the backups had thousands of changed files. It will be replaced with a rewrite of manifest file handling in 0.8-series.

Hi,

This option is already available in 0.8?

Best regards

I’m see that the Fix is Released. Has this feature been implemented?

Yes. A long time ago.

See https://gitlab.com/duplicity/duplicity. We moved years ago.