Please backport rdiff-backup for hardy
Bug #253464 reported by
kvdb
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Hardy Backports |
New
|
Undecided
|
Unassigned |
Bug Description
rdiff-backup (1.1.15-1) has a serious bug that keeps me from reliable backups. Often, when a previous backup hasn't been finished (due to network failure), rdiff-backup will crash on subsequent backups.
It's a bug that according to the author, has been fixed in 1.1.16:
'Finally fix 'No such file or directory' bug when attempting to regress after
a failed backup. (Patch from Josh Nisly)'
Please backport that version or the fix to hardy.
To post a comment you must log in.
rdiff-backup-1.2.0 is actually the newest version. I have followed https:/ /wiki.ubuntu. com/PackagingGu ide/Recipes/ DebianWatch to rebuild the package for you. It currently gives the following Lintian warning:
W: rdiff-backup source: changelog- should- mention- nmu nmu-has- incorrect- version- number 1.2.0-1
W: rdiff-backup source: source-
Since this is the first package I have rebuilt, I don't know how to fix that. The package however works fine and should fix your problem. I have attached .dsc and .deb.