rsync - Dec 2016 - [Bug 12472] New: invalid rsync-command syntax or options with —stats

https://bugzilla.samba.org/show_bug.cgi?id=12472

            Bug ID: 12472
           Summary: invalid rsync-command syntax or options with —stats
           Product: rsync
           Version: 3.1.2
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: core
          Assignee: wayned at samba.org
          Reporter: RutleCorps at gmail.com
        QA Contact: rsync-qa at samba.org

Client version 3.1.2
Server version 3.0.9
When using rsync 3.1.2 gives the error:
  /usr/local/s3rsync/prod-ssh-rsync3: invalid rsync-command syntax or options
By removing options, I was able to track the problem to the —stats flag.
It would be useful if the error message could report that —stats was the cause
of the error.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=12472

--- Comment #1 from Paul Slootman <paul at debian.org> ---
Did you cut&paste the --stats from some webpage? As you can see from the
emailed version of your report:

Summary: invalid rsync-command syntax or options with â\200\224stats

There's your problem! You're not using the ASCII '-' sign,
you're using some
UTF8 abomination that represents a dash only to humans.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=12472

--- Comment #2 from RutleCorps at gmail.com ---
(In reply to Paul Slootman from comment #1)

For the bug reporter, not in my rsync command.
(My rsync command is the same script that I used w/o error with 3.0.9)
I think the error has something to do with what's mentioned in the 3.1.2 man
page re: "—info=FLAGS"

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=12472

--- Comment #3 from RutleCorps at gmail.com ---
(In reply to Paul Slootman from comment #1)

Also, no error when the server side is 3.1.2, only when the server side is
3.0.9

-- 
You are receiving this mail because:
You are the QA Contact for the bug.