Hi there, On Mon, 11 Apr 2022, Matthew Pounsett wrote:
I seem to have encountered the same problem described in this thread which ends here: <https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32676.html> To summarize what I understand from that thread, there's a bug in File::RsyncP prior to some unidentified version that is exposed by a change in rsync as of 3.2.3. I've started running into the above-described issue since I upgraded one of my hosts to Debian Bullseye, which uses rsync 3.2.3. That host hasn't completed a backup since .. ... My backuppc host is still Debian Buster which has File::RsyncP 0.74. The thread above mentions that File::RsyncP is fixed in a recent version, but doesn't indicate what version that is. I'm trying to identify possible fixes for my issue here... and I'm wondering if simply upgrading my backup server to Bullseye is going to fix my problem, or if I should be grabbing libfile-rsyncp-perl and/or backuppc from backports, or what... Knowing which version of File::RsyncP fixes the issue would be a big help. Does anyone know that with certainty?
Looking at https://metacpan.org/dist/File-RsyncP/changes it seems that there is only one later version (0.76) so your options seem to be somewhat limited. :) The changelog mentions handling stderr output from rsync 3.2.3 but I haven't really investigated. On the File-RsyncP page there's a link http://perlrsync.sourceforge.net/ but it didn't seem very helpful (talks about version 0.68, Nov. 2006) so I don't know if the latest changes address your issue or not. -- 73, Ged. _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
