Hi,
Is there any way for duplicity to avoid showing errors when excluded
files can't be stat:ed? I don't see why not.
Also, how come the exit status of duplicity is 0 when I get e.g. this
error about a locked (but excluded, through the '**'):
address@hidden /etc/periodic/daily]$ FTP_PASSWORD=secret
PASSPHRASE=secret duplicity --encrypt-sign-key my_key --include
/home/dezeba --exclude '**' / scp://my.host/path
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Sat Oct 20 18:09:32 2012
Reuse configured PASSPHRASE as SIGN_PASSPHRASE
Error accessing possibly locked file /entropy
--------------[ Backup Statistics ]--------------
StartTime 1350749480.91 (Sat Oct 20 18:11:20 2012)
EndTime 1350749480.94 (Sat Oct 20 18:11:20 2012)
ElapsedTime 0.03 (0.03 seconds)
SourceFiles 2
SourceFileSize 520 (520 bytes)
NewFiles 0
NewFileSize 0 (0 bytes)
DeletedFiles 0
ChangedFiles 0
ChangedFileSize 0 (0 bytes)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 0
RawDeltaSize 0 (0 bytes)
TotalDestinationSizeChange 714 (714 bytes)
Errors 1
-------------------------------------------------
address@hidden /etc/periodic/daily]$ echo $?
0
I would really like it if Duplicity gave me an error exit status, my
scripts rely on this to report any errors to me by e-mail. Even if
it's a non-fatal error like this (since the file isn't even included
in the backup, I still want to get notified if Duplicity things
something's fishy). It even says "Errrors: 1" in its own output, so
why not exit with non-zero exit status?
You are correct. Would you mind posting a bug at
https://bugs.launchpad.net/duplicity and we'll get it fixed. It really should return a nonzero error code if there are any errors reported.
Besides this, thank you _so_ much for Duplicity. I love it!
You're welcome from the whole team here.
...Ken