The included github test case failed for me on vanilla rsync-3.2.7...
% ./test.sh
new.bin test.bin differ: byte 28345, line 1
% md5sum -b *.bin
7e11df4130968b5e4859f58b9bd6b453 *initial.bin
ff14ab080514d5681c99e4e1de01e29f *new.bin
151dd8b1c7bd628afcf38ac6c44155be *test.bin
% rsync --version
On Thu, Dec 8, 2022 at 12:49 PM Kevin Korb wrote:
> The first "Bug Fix" listed in https://rsync.samba.org/ftp/rsync/NEWS#3.2.4 is
> almost certainly related. Apparently it was fixed via remote option but
> since your test doesn't include networking that fix wouldn't help.
>
No, the bug was
Interesting, in that bug the problem was *solved* by adding
--no-whole-file when using --inplace and --sparse, whereas in my case
the problem is *caused* by using --no-whole-file alongside --inplace and
--sparse.
On 08/12/2022 20:48, Kevin Korb via rsync wrote:
The first "Bug Fix" listed in
The first "Bug Fix" listed in
https://rsync.samba.org/ftp/rsync/NEWS#3.2.4 is almost certainly
related. Apparently it was fixed via remote option but since your test
doesn't include networking that fix wouldn't help.
On 12/8/22 15:03, Mark Raymond via rsync wrote:
I believe I have found a
