On Wed, Jan 22, 2025 at 02:06:29PM -0500, Jeffrey Walton wrote:
> On Wed, Jan 22, 2025 at 12:23 PM Jon LaBadie <jo...@jgcomp.com> wrote:
> >
> > On Fedora 40:
> >
> > For years I've nightly updated copies of
> > three home directories using rsync.
> >
> > In yesterday's update, rsync updated to 3.4.0-1
> > and the nightly run failed on all three directories
> > with the following error message:
> >
> >    sending incremental file list
> >    Internal hashtable error: illegal key supplied!
> >    rsync error: errors with program diagnostics (code 13) at \
> >      hashtable.c(88) [generator=3.4.0]
> >
> > Reboot (not done after update) did not change things.
> > I downgraded rsync to 3.2.7-7 and the copy program ran normally.
> >
> > Anyone else seeing problems with rsync 3.4.0-1?
> 
> Possibly related, I believe glibc and gnulib recently merged changes
> to CRC code,[0] and it appears there's a problem in some code
> paths.[1]
> 
> I do not know if rsync uses glibc or gnulib code. I do not know if
> rsync even uses crc codes. It may be unrelated.
> 
> [0] <https://lists.gnu.org/archive/html/bug-gnulib/2024-11/msg00202.html>
> [1] <https://lists.gnu.org/archive/html/bug-gnulib/2025-01/msg00164.html>

I think this is https://github.com/RsyncProject/rsync/issues/697

and if so, it should be fixed in 3.4.1... which was pushed to f41 6 days
ago, but if you are on f40, it's still in testing: 

https://bodhi.fedoraproject.org/updates/FEDORA-2025-b28759cb95

So, a 'dnf --enablerepo updates-testing update rsync' should update you
on f40.

kevin
-- 
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to