duplicity-team team mailing list archive

[Michael Terry <mike@xxxxxxxxxxx>]

Ken: Please look at lp:~mterry/duplicity/list-old-chains -- it's a
first pass at keeping old chains and letting you list their contents.
The only missing bit from my perspective is an error if you try to
list from a backup chain that doesn't have a signature.  I'll add that
and file a merge request, but I'd appreciate you weighing in on this
issue.

Edgar: answers to your questions inline below.

2009/10/19  <edgar.soldin@xxxxxx>:
>> In Deja Dup, I'd like to be able to
>> list those old files; the next version will start automatically
>> creating multiple full backups for safety's sake, and I want to make
>> sure that all files are listable.
>
> Not sure what you mean here. Please explain.

Deja Dup has historically always done incremental backups.  But 11.0
will create occasional full backups (always keeping at least 2
around).

Eventually, however, I plan to add a feature that depends on listing
files in any particular timepoint.  I don't want to release a version
that creates backup chains that can't be listed, so I'm interested in
how/if duplicity plans to solve this.


>> I'd prefer to fix this in duplicity
>> for everyone, but if ya'll think it's undoable, I can do some hack,
>> like make separate directories in the backend for each full backup.
>> But that's more low-level than I wanted to be.  Seems like the same
>> thing could be done by not deleting sig chains.
>
> Also here? ...

Ken mentioned that one workaround is to create each full backup in its
own directory (thus duplicity wouldn't delete old sigs because it
wouldn't know about them).  So that's one solution.  But would require
me to change some bits in Deja Dup before I release 11.0 and generally
isn't user friendly.

I'd prefer to have duplicity just do the right thing.

-mt