rsync - Mar 2014 - Problem using --debug=FUZZY[2] flags

Hi,

I'm having a problem trying to get the --debug flags to work with 3.1.0. I
wanted to check with the mailing list to make sure this is really a bug and
not something I'm misunderstanding.

This is what I'm running (as a test):

rsync --fuzzy --fuzzy -vv --debug=FUZZY,FUZZY2 C_VOL-b001-i3818.spi
rsync://user at localhost/SHARENAME/dest

The "dest" folder on the destination side has a file named
C_VOL-b001-i3816.spi, which is just a copy of C_VOL-b001-i3818.spi that I
made and modified in a few places with a hex editor.

I don't get any fuzzy messages when running the command that way, but it
does utilize that file. To confirm, I commented out the "if
(DEBUG_GTE(FUZZY, 2))" line in generator.c (line 767 I believe) and rebuilt
- I get the "fuzzy size/modtime match for..." in the output then as
expected.
Does this look like a bug, or am I misunderstanding the new documentation
regarding how to use the --debug flags?

Thanks
Graham
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20140306/9bc0f71a/attachment.html>

On Thu, Mar 6, 2014 at 4:38 PM, Graham 5915 <graham5915 at gmail.com>
wrote:
> rsync --fuzzy --fuzzy -vv --debug=FUZZY,FUZZY2 C_VOL-b001-i3818.spi
> rsync://user at localhost/SHARENAME/dest
>
>
Check the rsync server's "max verbosity" setting in the daemon
config file.
 It needs to be at least "5" to allow that much chattiness (it
defaults to
1).  Also, FUZZY,FUZZY2 is contradictory, so FUZZY2 wins over FUZZY (aka
FUZZY1).

I'll look into mentioning "max verbosity" in the --info and
--debug
sections of the manpage.

..wayne..
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20140307/30cc806a/attachment.html>