aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2014-02-22 13:40:42 +0000
committerintrigeri <intrigeri@boum.org>2014-02-22 13:41:43 +0000
commit1a762885e26a6396e8e1798b51def7b103e92302 (patch)
tree5b22bb602a238c04440076a8c511fb635f9a6341
parente27654df5c688988fbab318d735b48f051a3d1f7 (diff)
downloadbackupninja-1a762885e26a6396e8e1798b51def7b103e92302.tar.gz
backupninja-1a762885e26a6396e8e1798b51def7b103e92302.tar.bz2
Make logic consistent with what we're using elsewhere.
Without this change, e.g. 0.5.20 would not get --extra-clean, while it should. Granted, the new test is buggy too, e.g. 0.7.1 will get --extra-clean, while it should not. Will report that to Redmine.
-rw-r--r--handlers/dup.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/handlers/dup.in b/handlers/dup.in
index 1ce7710..18afb98 100644
--- a/handlers/dup.in
+++ b/handlers/dup.in
@@ -191,7 +191,7 @@ else
fi
### Cleanup options
-if [ "$duplicity_major" -le 0 -a "$duplicity_minor" -le 6 -a "$duplicity_sub" -le 19 ]; then
+if ! [ "$duplicity_major" -ge 0 -a "$duplicity_minor" -ge 6 -a "$duplicity_sub" -ge 20 ]; then
execstr_options="${execstr_options} --extra-clean"
fi