Your message dated Sat, 11 Jul 2026 02:30:23 +0200 (CEST)
with message-id <[email protected]>
and subject line [solved] Bug#1141843: rsync: -c (checksum) option stopped
working
has caused the Debian Bug report #1141843,
regarding rsync: -c (checksum) option stopped working
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1141843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141843
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsync
Version: 3.2.3-4+deb11u4
Severity: grave
Justification: does not work
X-Debbugs-Cc: [email protected], [email protected]
I’ve been copying files between hosts for a while, both run
the same Debian versions so the package is identical between
both ends, and both are amd64 systems, updated today, current
kernel booted this week.
Today, I added the -c option to an otherwise identical command
to the one I was normally using, and…
+ /usr/bin/cleanenv / /usr/bin/rsync -zavPH --numeric-ids -S --stats
'--rsh=/usr/bin/ssh -T -i /root/.etc/$foo.key' --delete-after -x -c
$user@$host:/RS/ /RS/
receiving file list ...
invalid file mode 014704000000 for pi/config [Receiver]
rsync error: protocol incompatibility (code 2) at flist.c(867) [Receiver=3.2.3]
The file should not be all that unexpected:
root@$host:/RS # ls -ln pi/config
-r-------- 1 110 119 155 Jun 4 2024 pi/config
The error message looks to be an off-by-16-bits to me.
This is complete failure to synchronise with checksumming,
which is required in some circumstances, hence the severity.
-- System Information:
Debian Release: 11.11
APT prefers oldoldstable-updates
APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable-security'),
(500, 'oldoldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-45-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages rsync depends on:
ii init-system-helpers 1.60
ii libacl1 2.2.53-10
ii libc6 2.31-13+deb11u14
ii liblz4-1 1.9.3-2
ii libpopt0 1.18-2
ii libssl1.1 1.1.1w-0+deb11u8
ii libxxhash0 0.8.0-2
ii libzstd1 1.4.8+dfsg-2.1
ii lsb-base 11.1.0
ii zlib1g 1:1.2.11.dfsg-2+deb11u2
rsync recommends no packages.
Versions of packages rsync suggests:
ii openssh-client 1:8.4p1-5+deb11u7
ii openssh-server 1:8.4p1-5+deb11u7
ii python3 3.9.2-3
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 11 Jul 2026, Thorsten Glaser wrote:
>My apologies; turns out that that one special user
>has a command= in its authoried_keys server-side
>which points to a user-local copy of rsync with
>extra capabilities so it can read the source tree.
Oh, aaaaaaaaaaaaaaaaah. I blame the heat, and that it’s
been a while since I initially set up the sync between
these systems and had not needed -c yet, and that I did
it different for these than I used to do.
Of COURSE adding -c also changes the command sent to the
server.
When having command="…" in authorized_keys, it does of
course include the flags.
(Used to use anoncvssh which allowed only cvs, svn, git,
rsync, and checked for a few sets of flags instead of
hardcoding the set to use.)
OK, problem solved, it now syncs (or, rather, is still
checksumming for the file list).
I just wish the protocol made mismatches like that easier
to debug, it didn’t even output the sender version in all
those error messages… nothing you can do of course, even
more so as upstream is now slop.
Sorry for taking up the time, but I found *so few* info
on the net for these error messages… maybe someone in the
future will find this.
bye,
//mirabilos
--
[16:04:33] bkix: "veni vidi violini"
[16:04:45] bkix: "ich kam, sah und vergeigte"...
--- End Message ---
