[Duplicity-talk] Strange behaviour when specifying a timestamp

[Eric B.]

A couple of things I have encountered as I am testing out the -t option with 
duplicity.  I am not sure if it is my interpretation of the docs, or if they 
are bugs in duplicity itself.

1) I was hoping to generate a list of files in the backup given a particular 
timestamp.  ie:
# duplicity list-current-files -t2008-03-13 
file:///duplicity/test --no-encryption

However, this gives me a list of files all currently backed up by duplicity; 
not the list as at 2008-03-13 backup, which I would have expected.  Is 
browing list of files based on timestamp not a supported feature?


2) I tried to restore files given a particular timestamp.  I was expecting 
duplicity to restore all files backup up at that timestamp.  According to 
the docs, if only a date is given, the restore will be taken at midnight of 
that date.  So -t2008-03-13 would imply 2008-03-13T00:00 :00-04:00 would it 
not?  (I am in EDT).  Or would that imply 2008-03-13T00:00:00-00:00?

# duplicity restore -t2008-03-13 file:///duplicity/test --no-encryption 
/tmp/dup

I would therefore have expected the last backup prior to 2008-03-13T00:00 
:00-04:00 to be restored.  However, in my case, the first backup was made at 
2008-03-13T10:58:04-04:00.  So I was expecting nothing to be restored. 
However, duplicity still restored everything from my 
2008-03-13T10:58:04-04:00 backup.  Is this expected behaviour?  Even if I 
specify the full timestamp as 2008-03-13T00:00 :00-04:00, the first backup 
from 10:58:04-04:00 is still restored.


Thanks for the clarification.

Eric