samba-bugs at samba.org
2016-Mar-27  10:52 UTC
[Bug 11812] New: rsync without --verbose still writes "(new) backup_dir is ..." to STDOUT
https://bugzilla.samba.org/show_bug.cgi?id=11812
            Bug ID: 11812
           Summary: rsync without --verbose still writes "(new) backup_dir
                    is ..." to STDOUT
           Product: rsync
           Version: 3.1.2
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: core
          Assignee: wayned at samba.org
          Reporter: mi.lists.bugzilla at alma.ch
        QA Contact: rsync-qa at samba.org
rsync always writes "(new) backup_dir is ..." to STDOUT. Is this
really
necessary?
    rsync -a --delete --backup --backup-dir="_before-$(date +%F)"
$source $dest
    (new) backup_dir is _before-2016-03-27
This seems to have appeared in 3.1.1, which created the directory even if it
was not needed (see bug #11423).
Version 3.1.2 doesn't create useless backup-dirs any more, but if it does it
reports it to STDOUT which is also quite useless. We have --verbose when we
want to check what is going on. If everything works alright, I feel that rsync
without -v should remain silent, as is customary in Unix tools.
-- 
You are receiving this mail because:
You are the QA Contact for the bug.
samba-bugs at samba.org
2016-Apr-17  18:09 UTC
[Bug 11812] rsync without --verbose still writes "(new) backup_dir is ..." to STDOUT
https://bugzilla.samba.org/show_bug.cgi?id=11812
Wayne Davison <wayned at samba.org> changed:
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
--- Comment #1 from Wayne Davison <wayned at samba.org> ---
Yeah, that print needs this check: if (INFO_GTE(BACKUP, 1))
Fix committed to git (0f7db203fb4125e9ec8851bb0ff8878258fc4a05).
-- 
You are receiving this mail because:
You are the QA Contact for the bug.