Description of problem: If "use chroot= yes" is set for the server then it will be able to set permissions on received files. The problem is that glibc in F33 now implements lchmod, but badly by emulation using /proc, and that fails in a chroot as /proc is not available. In F32 glibc didn't implement lchmod and rsync's configure script fell back to an alternative way of setting the permissions. Version-Release number of selected component (if applicable): glibc-2.32-1.fc33.x86_64 Steps to Reproduce: 1. Create a server target with chroot enabled 2. Sync a file to it 3. See that the permissions are wrong Actual results: Permissions are set to 0600. Expected results: Permissions are set to match the source, or whatever "incoming chmod" said to set them to. Additional info: Already reported in Ubuntu as https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1902109 and as a glibc issue at https://sourceware.org/bugzilla/show_bug.cgi?id=26401.
Also upstream at https://github.com/WayneD/rsync/issues/109 and rsync upstream has now disabled lchmod for linux in https://github.com/WayneD/rsync/commit/85b8dc8abaca96fc3ea7421e09101b6ac41b6718.
Hi Tom, thanks for the report, fix is on the way. I am testing the improved upstream fix right now: https://github.com/WayneD/rsync/commit/9dd62525f3b98d692e031f22c02be8f775966503
FEDORA-2020-d34606ef29 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d34606ef29
*** Bug 1904344 has been marked as a duplicate of this bug. ***
FEDORA-2020-d34606ef29 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-d34606ef29` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d34606ef29 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-d34606ef29 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.