Package: obnam Version: 1.0-1 Severity: minor Tags: patch Dear Lars,
Please find attached a patch for a small try to make the manpage about the keeping policy more clear. Hope it helps, Damien -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (450, 'stable-updates'), (450, 'stable'), (300, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages obnam depends on: ii libc6 2.13-33 ii python 2.7.2-10 ii python-cliapp 0.29-1 ii python-larch 1.20120527-1 ii python-paramiko 1.7.7.1-2 ii python-tracing 0.6-2 ii python-ttystatus 0.18-1 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 obnam recommends no packages. obnam suggests no packages. -- no debconf information
=== modified file 'obnam.1.in' --- obnam.1.in 2012-04-29 19:12:21 +0000 +++ obnam.1.in 2012-06-23 10:15:59 +0000 @@ -336,7 +336,14 @@ .PP A typical policy might be .IR 72h,7d,5w,12m , -to keep hourly backups for three days, +which means: keep +the last 72 hourly backups, +the last 7 daily backups, +the last 5 weekly backups and +the last 12 monthly backups. +If the backups are systematically run on an hourly basis, +this will mean keeping +hourly backups for three days, daily backups for a week, weekly backups for a month, and monthly backups for a year.
