Re: [Duplicity-talk] How is --file-changed supposed to work?

[edgar . soldin]

On 17.11.2015 05:58, Nate Eldredge wrote:
> It appears from the duplicity man page that collection-status has an option 
> --file-changed, which apparently should list the various versions of the 
> specified file that are backed up.  

seems to be a new addition by Ken. 

when i try it, i get only the latest change in the backup however, e.g.

--- Start running command STATUS at 10:58:03.094 ---
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Tue Nov 17 10:56:14 2015
-------------------------
File: release.sh
Total number of backup: 1
 Type of backup set:                            Time:  Type of file change:
                Full         Tue Nov 17 10:56:14 2015                   New
-------------------------
--- Finished state OK at 10:58:04.293 - Runtime 00:00:01.198 ---


>However I cannot seem to get it to work.

the manpage text at least

"
This option may be given in collection-status mode, causing only path status to 
be collect instead of the entire contents of the backup archive. path should be 
given relative to the root of the directory backed up.
"

suggests that it shows changed file instances over multiple backup chains.
 
> # duplicity collection-status --tempdir=/mnt/blob/tmp 
> --archive-dir=/mnt/blob/cache --file-changed=bin/ls 
> file:///space/duplicity/historic/mercury-freebsd
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Wed Nov  2 22:00:00 2005
> -------------------------
> File: bin/ls
> Total number of backup: 0
>  Type of backup set:                            Time:  Type of file change:
> -------------------------
> 
> But bin/ls does appear when I do list-current-files (keeping --tempdir, 
> --archive-dir and url the same), and it is restored when I restore this url.  
> So shouldn't I see something here?  I also tried "/bin/ls" and "./bin/ls".
> 
> (By the way, I noticed this while trying to debug another backup, where files 
> were not restored although I thought they existed.  I thought perhaps I had 
> deleted the files at some point before the latest incremental, so I thought 
> --file-changed would tell me if the files were in any of my incrementals.)
> 
> I am using duplicity 0.7.05 on ubunutu trusty (package 
> 0.7.05-0ubuntu0ppa1130~ubuntu14.04.1 from the ppa).
> 

let's see what Ken says how it is supposed to work.


..ede/duply.net