Description of problem: Currently EPEL distributes version 1.0.5 of rdiff-backup.. However the latest stable release is version 1.2.8 As I'm using an external backup service (rsync.net) which provides rdiff-backup 1.2.8 on their side as a backup mechanism. Also rdiff-backup 1.0.5 was released in November 2006!! where as rdiff-backup 1.2.8 was released in March of 2009. From the rdiff-backup FAQ::: # Is rdiff-backup backwards compatible? In general, rdiff-backup does not strive to make newer clients compatible with older servers (or vice versa). However, there is no intention to purposefully make different versions incompatible across the network -- changes are introduced primarily to fix bugs or introduce new features that cannot be implemented without breaking the network protocol. Furthermore, rdiff-backup does try to make it possible to read older archives. When running as a client, rdiff-backup checks the version of rdiff-backup running on the server, and prints a warning message if the two versions are different. If you have any problems with your backup, it is strongly recommended that you upgrade the older version before reporting any issues.
Sadly, the issue here is that if I update EPEL to the new version, all the people using the 1.0.5 version won't be able to talk to it anymore. ;( So, the solution is a parallel installable 1.2.8 package, but I just haven't had time to finish putting one together. ;( Marking this a dup of the exisiting bug and hopefully I can get something soon... Sorry for the problems. *** This bug has been marked as a duplicate of bug 466720 ***