Correct.
Rdiff-backup only guarantees compatibility between stable releases, eg:
1.2.0, 1.2.1, and 1.2.2 are compatible together and 1.0.5, 1.0.4, 1.0.3,
etc.. The development series, 1.1.x, came with no backwards-compatible
guarantees.
Ubuntu was shipping development releases, and can either upd
This means you're dropping backward compatibility for an old version. This bug
occured in my setup because I was trying to get rdiff-backup from feisty (which
isn't that ancient) to operate on an rdiff-backup tree created by an older
(sarge?) version of rdiff-backup.
My testing environment howev
Given that Jakob was using a non-standard version, I am marking this bug
as invalid. Many people use --remove-older-than without trouble ... this
traceback indicates that there was a bug in the Python code (not due to
the backup repository). I assume it was due to Jakob's modifications.
** Changed
Removing confirmation - I was inadvertently using a non-standard rdiff-
backup version when confirming this bug.
** Changed in: rdiff-backup (Ubuntu)
Status: Confirmed => New
--
rdiff-backup crashes while accessing old data
https://bugs.launchpad.net/bugs/119885
You received this bug noti
rdiff-backup in dapper amd64 crashes when trying to remove old increments.
Therefore, the backup grows out of bounds, so you have to manually delete
increments every now and then.
# rdiff-backup --remove-older-than 1M /backup/rdiff-backup
Exception 'SingleSetGlobals instance has no attribute 'src
