Public bug reported:
Binary package hint: rdiff-backup
When one runs "rdiff-backup --list-increments /path/to/backup/archive",
it will often fail to run in situations where "rdiff-backup --list-
increment-sizes" will succeed. An interrupted backup, currently-running
backup, or other recoverable situation will cause -l to throw an
exception and exit with a return code of 1 -- indistinguishable from an
unrecoverable error.
In order to work around this and usefully get a value for the date of
the most recent useful backup for an archive (the current moment if a
backup is currently still running, and the most recent incremental if
the previous backup was interrupted), I had to write a python program
that re-implemented Main.checkdest_need_check() and regress.check_pids()
with versions that merely returned status codes rather than abort
completely.
This sort of behavior needs to be part of rdiff-backup from the start,
as busy backup locations often appear to be unworkably broken to the
command-line tools even when everything is perfectly fine.
** Affects: rdiff-backup (Ubuntu)
Importance: Undecided
Status: New
--
rdiff-backup --list-increments does not distinguish between error conditions
https://bugs.launchpad.net/bugs/128244
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
