[Bug 13147] inconsistent behaviour regaring vanished files information

2017-11-28 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=13147 --- Comment #4 from roland --- mhh, if the error is not a warning but an error, the offending file is shown (for the warning of vanished files, the warning itself goes to stderr but the vanished filename goes to stdout). but only on OSX why that d

[Bug 13147] inconsistent behaviour regaring vanished files information

2017-11-25 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=13147 --- Comment #3 from roland --- apparently, ssh as a transport is the culprit, as it doesn`t happen with rsync in daemon mode. i found some osx related ticket on "stderr/stdout merge" ( https://github.com/ansible/ansible/issues/14960 ) after furt

[Bug 13147] inconsistent behaviour regaring vanished files information

2017-11-25 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=13147 --- Comment #2 from roland --- it`s also no linux->osx interacting issue, the problem also appears when doing rsync on osx via ssh/localhost. but why ? ssh & osx does handle stdout and stdout correctly, as shown here: gonzo:tmp root# ssh root@

[Bug 13147] inconsistent behaviour regaring vanished files information

2017-11-25 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=13147 --- Comment #1 from roland --- i searched into this a little bit and it`s not a problem with differing rsync versions, it also happens with rsync 3.1.2 (linux) -> rsync 3.1.2 (osx) what i found is, that rsync 3.1.2 behaves correctly when run on os