On Friday, August 02, 2019 06:13:53 AM Otto Kekäläinen wrote: > With the adoption of librsync2 the old MD4 hash is no longer supported > and thus a non-backwards compatible change is introduced. All backups > must therefore start from "scratch". > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776246
I read a little bit of that reference, but maybe not enough to fully understand. Some questions: * has rdiff already switched to libsync2 or is this something you are planning? * the main one: if the change is made, does that mean that some old backups will no longer work and have to be redone? * related to above (maybe): that link says that (iiuc) libsync2 can read the old md4 hash but (on rewriting) it will write the new hash (whatever it is called) -- does that mean that old backups will remain readable? > > Also, the Python 3 rewrite is a major thing. Therefore I suggest the > next release of rdiff-backup would bump the major version number and > become 2.0.0 (or even 3.0.0 to tribute Python 3). > > What do you think? > > - Otto > > _______________________________________________ > rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users > Wiki URL: > http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki _______________________________________________ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
