[Bug 1300768] Re: Rsync fails with (very) old server.

[rew]

I got the git upstream sources. 
I used "git bisect" for the first time. 
Out of 356 commits between 3.0.9 and the current version.... 

[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.

.... is the one that causes the problem.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1300768

Title:
  Rsync fails with (very) old server.

Status in “rsync” package in Ubuntu:
  New

Bug description:
  
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1300768/+subscriptions