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

Reply via email to