[Bug 11812] New: rsync without --verbose still writes "(new) backup_dir is ..." to STDOUT

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 11812] New: rsync without --verbose still writes "(new) backup_dir is ..." to STDOUT

samba-bugs
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: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

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.

--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Reply | Threaded
Open this post in threaded view
|

[Bug 11812] rsync without --verbose still writes "(new) backup_dir is ..." to STDOUT

samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=11812

Wayne Davison <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Wayne Davison <[hidden email]> ---
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.

--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html