Comment 18 for bug 1652410

>> To fix this bug from happening in the future, we could perhaps
>> restrict the file list that is passed from Déjà-Dup to duplicity
>> collection-status? Perhaps to *.{diff,sig}tar.{gz,gpg} and
>> *.manifest files only, or something like that?

> This sounds good to me!

On further investigation, unfortunately, I realize it is not a file list that Déjà-Dup passes to duplicity collection-status, but the path/URL of the backup repository, e.g.:

  duplicity collection-status [options] file://home/luke/deja-dup

This is what duplicity expects for this action, according to the man page. So it might be trickier than I thought to have duplicity not examine certain files, and perhaps this bug would be better solved on duplicity's side than on Déjà-Dup's side.

Worst case, if the bug can't be fixed and the situation requires a human to examine the contents of the backup repository to take adequate action, then duplicity should return a more descriptive message than the current terse assertion error.