Ken, is this intended behavior? Seems like a situation where duplicity should defer to the backup's manifest status (i.e. it's gone). Is there something Deja Dup can do to be smarter about this?
Ken, is this intended behavior? Seems like a situation where duplicity should defer to the backup's manifest status (i.e. it's gone). Is there something Deja Dup can do to be smarter about this?