[rdiff-backup-users] FW: Bug#194019: --remove-older-than gives a fatal error if there is nothing to be done

[John Goerzen]

Any insight on this one?

----- Forwarded message from Matt Zimmerman <address@hidden> -----

From: Matt Zimmerman <address@hidden>

Package: rdiff-backup
Version: 0.10.1-3
Severity: normal

I have a backup system which iterates over a number of directories and uses
rdiff-backup to make backups of them.  Occasionally, a new directory is
added to the batch.

I would like to, after each run, use --remove-older-than to trim the oldest
of the backups, and keep a rolling archive of the last <period of time>.
When I add a new directory, though (or if I were to increase the period of
time), rdiff-backup blows up, saying (e.g.):

Fatal Error: No increments older than Tue Apr 15 11:08:15 2003 found

It seems like this should not be an error condition; there is simply nothing
to be deleted, and I do not need to receive mail from cron telling me about
this.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux there 2.4.20-1-686 #1 Sat Mar 22 13:16:21 EST 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US (ignored: LC_ALL set)

Versions of packages rdiff-backup depends on:
ii  libc6                         2.3.1-17   GNU C Library: Shared libraries an
ii  librsync1                     0.9.5.1-3  Binary diff library based on the r
ii  python2.2                     2.2.2-6    An interactive object-oriented scr
ii  rdiff                         0.9.5.1-3  Binary diff tool for signature-bas

-- no debconf information


-- 
 - mdz


----- End forwarded message -----