You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The --fileflags patch seems to mix-up the copied BSD flags at least during a remote rsync.
In flist.c: While the sender serialises the file's metadata in the order of mode, file flags and then (optionally) atime, the patch reads this serialisation on the receiver side in the wrong order of mode, atime and then flags. This means that in case one uses the corresponding sync option to send atimes for files, the patch interprets the atime value as the BSD flags.
Solution:
In flist.c:recv_file_entry(), move the fileflag receiving code
The --fileflags patch seems to mix-up the copied BSD flags at least during a remote rsync.
In flist.c: While the sender serialises the file's metadata in the order of mode, file flags and then (optionally) atime, the patch reads this serialisation on the receiver side in the wrong order of mode, atime and then flags. This means that in case one uses the corresponding sync option to send atimes for files, the patch interprets the atime value as the BSD flags.
Solution:
In flist.c:recv_file_entry(), move the fileflag receiving code
about 15 lines up just after this condition:
Environment: rsync-3.2.7.tar.gz + fileflags patch (rsync-patches-3.2.7.tar.gz, Jan 2023), macOS 12.6, arm64
The text was updated successfully, but these errors were encountered: