Control: severity -1 normal Hello Eugene, thanks for your bug report :)
I think I still need to understand a few things before proceeding, seems like there's something weird going on in your system. 1) Do you know how is it possible that you were running Debian testing with libc6 2.30-4? Even Debian stable has a newer version, I believe you could have missed running apt full-upgrade at some point. 2) Is your system under a chroot and/or without /proc mounted? We've had this issue in the near past [0], but it should be patched for 3.2.3-7 [1], even with older libc6. > Upgrade libc6 to 2.32-4 solves the problem. That's the current version available in testing and unstable, so anybody running those will be fine. Stable currently has libc6 2.31, and I plan on having a backports of rsync at some point in the future, so this issue could affect that, though I don't see how the changes between 3.2.3-4 and 3.2.3-7 could trigger this bug. I'm also considering that upstream's bug reports says this issue only started with libc6 2.32 [0][2]. If anything, 3.2.3-7 is fixing the very same issue you reported, which should have been happening in rsync 3.2.3 + libc6 2.32 (but you mention you had an older libc6). Overall I believe there might be something wrong in your system, related to libc6. I will lower the priority to normal, considering all of these, and will increase it if needed once we understand your issue better. [0] https://github.com/WayneD/rsync/issues/109 [1] https://salsa.debian.org/debian/rsync/-/commit/3320a1c1b9e9fcf4b4b759a194a6059380c56b88 [2] https://sourceware.org/bugzilla/show_bug.cgi?id=26401 Thank you, -- Samuel Henrique <samueloph>
