Comment 7 for bug 1526557

Not as it was implemented. Way too much memory use!

On Tue, Jan 28, 2020 at 12:35 PM Anthony <email address hidden> wrote:

> *** This bug is a duplicate of bug 1044715 ***
> https://bugs.launchpad.net/bugs/1044715
>
> So this option will not be added in 0.8? :X
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1526557
>
> Title:
> --file-changed does not work
>
> Status in Duplicity:
> Invalid
>
> Bug description:
> Duplicity 0.7.06
> Ubuntu 14.04
> Python 2.7.6
>
> The --file-changed option with collection-status does not work.
> Restoring files work just fine.
>
> Several months of daily backups are available when testing this.
>
> $ duplicity collection-status --file-changed home/user/filename --gio
> sftp://user@server/home/user/backups
> Warning: Option --gio is pending deprecation and will be removed in a
> future release.
> Use of default filenames is strongly suggested.
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Mon Oct 5 09:38:37 2015
> -------------------------
> File: home/user/filename
> Total number of backup: 0
> Type of backup set: Time: Type of file
> change:
> -------------------------
>
> $ duplicity restore --file-to-restore home/user/filename --gio
> sftp://user@server/home/user/backups restored_file
> Warning: Option --gio is pending deprecation and will be removed in a
> future release.
> Use of default filenames is strongly suggested.
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Mon Oct 5 09:38:37 2015
>
> This should be easily reproduced. I noted someone else having the same
> problem: https://lists.gnu.org/archive/html/duplicity-
> talk/2015-11/msg00008.html
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1526557/+subscriptions
>