rdiff-backup --list-increments does not distinguish between error conditions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rdiff-backup (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: rdiff-backup
When one runs "rdiff-backup --list-increments /path/to/
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_
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.
Changed in rdiff-backup: | |
status: | Incomplete → In Progress |
Hi Nick,
This is a good point about the two different behaviors and I agree that --list- increment- sizes is more sensible.
I think the correct fix is to simply remove the call to restore_ check_backup_ dir() in the ListIncrements(rp) function in Main.py. If you remove that line, does the bothersome behavior go away?
If that works for you (and I'm pretty sure it will), I will remove that line in CVS, which will become rdiff-backup 1.1.13 and subsequent releases.
Thanks for noticing this!
Andrew