Hi Samuel. On Sat, Sep 25, 2021 at 03:08:47PM +0100, Samuel Henrique wrote: > 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.
I have several hosts with old kernels (like 4.17) and their headers, and gcc-7, which are tied to libc6-2.30 by their dependences. On "aptitude install libc6" first resolver's proposal was to remove these packages. I agreed with this choice to install libc6-2.32. I have a copy of one such system on backup, it may be studied for more details if need... However, it looks pointless, because support for lchown() is definitely a new feature, so the right way, IMHO, is to correct dependences for rsync package: "libc6 (>= 2.31)". > 2) Is your system under a chroot and/or without /proc mounted? No, fault happens with physical hosts (not VMs or containers), where /proc is mounted. However, they are all running SysV init. > > 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. Right. I also have some similar hosts with libc-2.32, probably they were upgraded to last version due to absence of old kernels, old gcc, etc. Rsync runs fine on them. > 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. Every system with periodic updates might have outdated packages, generally it's not a problem (and should not be a problem) if binary API is compatible and all package dependences are correct. -- Eugene Berdnikov
