diff options
| author | intrigeri <intrigeri@boum.org> | 2010-05-06 19:37:33 +0200 |
|---|---|---|
| committer | intrigeri <intrigeri@boum.org> | 2010-05-06 19:37:57 +0200 |
| commit | 6cf9c8988b137e42f0d29ade910d2a4f50372798 (patch) | |
| tree | 7e5e2a69d1408d832f253c04e0e68ceb85d582b9 | |
| parent | acd5a7e2e4f8d951ada9b4e485f29b3a9a425c00 (diff) | |
| download | backupninja-6cf9c8988b137e42f0d29ade910d2a4f50372798.tar.gz backupninja-6cf9c8988b137e42f0d29ade910d2a4f50372798.tar.bz2 | |
Added NEWS item about the new duplicity archive directory location.
| -rw-r--r-- | NEWS | 16 |
1 files changed, 16 insertions, 0 deletions
@@ -1,3 +1,19 @@ +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. + 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: + + mv /root/.cache/duplicity /var/backups/ + backupninja (0.9.7-1) UNRELEASED * mysql: output filenames to support shell meta-characters in |