Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
backupninja
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Liberate
backupninja
Commits
b87d3648
Commit
b87d3648
authored
14 years ago
by
intrigeri
Browse files
Options
Downloads
Patches
Plain Diff
Update Debian NEWS and changelog.
parent
6275acd0
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
debian/NEWS
+22
-0
22 additions, 0 deletions
debian/NEWS
debian/changelog
+26
-0
26 additions, 0 deletions
debian/changelog
with
48 additions
and
0 deletions
debian/NEWS
+
22
−
0
View file @
b87d3648
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 <micah@riseup.net> 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
...
...
This diff is collapsed.
Click to expand it.
debian/changelog
+
26
−
0
View file @
b87d3648
backupninja (0.9.8-1) unstable; urgency=low
* Bump Standards version: no changes
* New upstream release
. only run mdadm if RAID devices actually exist (Closes: #572450)
. duplicity handler now defaults to use --full-if-older-than
(Closes: #572523, #535996)
. duplicy handler now gets rid of unnecessary old cache files
(Closes: #572721)
. fix duplicity version comparison (Closes: #578987)
. duplicity now uses /var/cache/backupninja/duplicity as a cache
directory (Closes: #580016)
. allow to securely transmit the FTP password from backupninja to
duplicity (closes an unreported security issue)
. mysql handler does not lock tables in the information_schema
database anymore (Closes: #587011)
. mysql dbusername/dbpassword options are now actually usable
. include the rsync handler (Closes: #515108)
. prevents multiple instances of the same rsync job to run in
parallel
. avoid passing the remote user twice to rsync-over-ssh
. documentation improvements (Closes: #583778)
. support systems that lack gzip's --rsyncable option
-- Micah Anderson <micah@riseup.net> Sun, 12 Sep 2010 19:58:49 +0200
backupninja (0.9.7-5) unstable; urgency=low
* Upload experimental package to unstable
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment