aboutsummaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2010-05-10 22:15:41 +0200
committerintrigeri <intrigeri@boum.org>2010-05-10 22:15:41 +0200
commitd6ec2b4e62d1de94cf731381d7da934b6fee7ddc (patch)
treed12f5340b856dbc032056fd7fec70ca070612663 /NEWS
parent99434c8b07f29fd45d1db55b30b5820a47d5a1ab (diff)
downloadbackupninja-d6ec2b4e62d1de94cf731381d7da934b6fee7ddc.tar.gz
backupninja-d6ec2b4e62d1de94cf731381d7da934b6fee7ddc.tar.bz2
Store duplicity cache to /var/cache/backupninja/duplicity.
... instead of previous /var/backups/duplicity.
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS7
1 files changed, 4 insertions, 3 deletions
diff --git a/NEWS b/NEWS
index 50739f4..0ec3a81 100644
--- a/NEWS
+++ b/NEWS
@@ -3,8 +3,8 @@ backupninja (0.9.8-1) UNRELEASED
* duplicity 0.6.01 and later defaults to using an archive (cache)
directory, which was previously opt-in. Starting with backupninja
0.9.8, the backupninja duplicity handler puts this cache into
- /var/backups/duplicity unless specified by the user with the "options"
- setting the *.dup job.
+ /var/cache/backupninja/duplicity unless specified by the user with
+ the "options" setting the *.dup job.
When backups have been performed with backupninja older than 0.9.8 in
conjunction with duplicity 0.6.01 or later, e.g. when using Sid or
Squeeze at certain times of the Squeeze release cycle, cache files
@@ -12,7 +12,8 @@ backupninja (0.9.8-1) UNRELEASED
delete these files, or rather save bandwidth and just move the cache
directory to the new location:
- mv /root/.cache/duplicity /var/backups/
+ mkdir -p /var/cache/backupninja
+ mv /root/.cache/duplicity /var/cache/backupninja/
backupninja (0.9.7-1) UNRELEASED