Comment 2 for bug 1004210

The problem exists in backupninja 1.0.1-2 on 16.04 xenial. Because of this duplicity 0.7.06 fails to be recognized as >= 0.6.17, causing it to assume that only the scp/sftp backend is supported and paramiko isn't (06 ! -ge 17) and that it can't handle removing increments older than full backups (06 ! -ge 10).

The fix has been sitting in their git repo since 2014-Feb-22 [0]. The old upstream source location points to this new location. [1]

This isn't the only bug in 1.0.1 that has a fix available but is waiting a 1.0.2 release. There is also a host.rsync bug. [2]

0) https://0xacab.org/riseuplabs/backupninja/commit/1017ec315fe2b5550908abd9f1f4f9e5edb0bd9d
1) https://labs.riseup.net/code/projects/backupninja
2) https://scriptthe.net/2015/02/09/backupninja-or-how-i-learned-to-stop-worrying-and-build-from-source/