[Bug 10532] New: Rsync fails with older version.
samba-bugs at samba.org
samba-bugs at samba.org
Tue Apr 1 09:40:41 MDT 2014
https://bugzilla.samba.org/show_bug.cgi?id=10532
Summary: Rsync fails with older version.
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: r.e.wolff at bitwizard.nl
QAContact: rsync-qa at samba.org
Does not work:
Trusty Tahr.
Rsync version 3.1.0
Protocol version 31
DOES work:
Saucy
rsync version 3.0.9
protocol version 30
In both cases: "server side":
Suse 7.0
version 2.3.2
protocol version 21
with both "client" side rsyncs I of course get:
> Server is very old version of rsync, upgrade recommended.
but with the newer rsync I get:
Warning: No xauth data; using fake authentication data for X11 forwarding.
Server is very old version of rsync, upgrade recommended.
protocol version mismatch - is your shell clean?
(see the rsync man page for an explanation)
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(226)
[Receiver=3.1.0]
According to the manpage I can test the "is your shell clean" with
ssh oldserver /usr/bin/true > out.dat
but I get a clean file (0 bytes).
I just checked: the "no xauth data" doesn't matter:
rsync -e "ssh -x" vsuse:/etc/issue .
has the same problems.
The Ubuntu guys asked me to report this here....
I used "git bisect" for the first time. The commit that caused this problem is:
[8b3e60523aa3d86583a1df54c81c9d480ea19740] Improved the fix that ensures that
the generator gets notified about an I/O error for the incremental directory
that generated the error. The PROTOCOL_VERSION was bumped to 31 to implement
this.
See https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1300768 for my
original ubuntu bugreport. (but mostly copy-pasted here).
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the rsync
mailing list