From b87d36489ba1f584e6cfe3fec54de49dc9d1a2a6 Mon Sep 17 00:00:00 2001 From: intrigeri Date: Sun, 12 Sep 2010 20:13:16 +0200 Subject: Update Debian NEWS and changelog. --- debian/NEWS | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) (limited to 'debian/NEWS') diff --git a/debian/NEWS b/debian/NEWS index 7b0b76e..c621881 100644 --- a/debian/NEWS +++ b/debian/NEWS @@ -1,3 +1,25 @@ +backupninja (0.9.8-1) unstable; urgency=low + + * 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/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 + were probably saved into /root/.cache/duplicity; one may want to + delete these files, or rather save bandwidth and just move the cache + directory to the new location: + + mkdir -p /var/cache/backupninja + mv /root/.cache/duplicity /var/cache/backupninja/ + + It is probably desirable to exclude this cache directory from + duplicity backup sets to avoid some kind of reentrant backup problem. + + -- Micah Anderson Sun, 12 Sep 2010 19:58:49 +0200 + backupninja (0.9.4-1) unstable; urgency=low * duplicity: Old (pre-0.9.4) example.dup file used to give false -- cgit v1.2.3