Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10748 - rdiff-backup problem while migrating existing system data from Ubuntu to Arch Linux

Attached to Project: Community Packages
Opened by Cliff Cunnington (cliffix) - Tuesday, 24 June 2008, 07:07 GMT
Last edited by Aaron Bull Schaefer (elasticdog) - Tuesday, 29 July 2008, 17:11 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Aaron Bull Schaefer (elasticdog)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After running the Arch version of rdiff-backup (1.0.5/stable) on a backup created with the Ubuntu Gutsy version of rdiff-backup (1.1.5), my existing backup archive was damaged. Backups created on Debian Etch will likely have the same problem.


My quick solution:
I modified this community PKGBUILD, added it to my ABS and used makepkg to package a more recent "unstable" version of rdiff-backup (1.1.16). After installing 1.1.16, running rdiff-backup recovered the damaged archive: "Previous backup seems to have failed, regressing destination now."


I flagged the current Arch community version of rdiff-backup as being out-of-date, but the maintainer may prefer to add a rdiff-backup.install with a warning of potential damage to archives created with Ubuntu/Debian/other(?) installations.

Additional info:
* rdiff-backup 1.0.5

Steps to reproduce:
1. Run rdiff-backup-1.0.5 on a destination directory created with Ubuntu (>= dapper) or Debian (>= etch).
2. To recover damaged archive, use ABS / makepkg to build more recent package and re-run rdiff-backup.
This task depends upon

Closed by  Aaron Bull Schaefer (elasticdog)
Tuesday, 29 July 2008, 17:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  A new stable version has been released upstream and has been pushed to the community repo. There is no longer a need to worry about this incompatibility between distributions and whether or not they support the development version versus the stable release.

Loading...