Rpm spits informative garbage to stdout instead of stderr

[pmatilai]

Originally reports include but are by no means limited to:
https://bugzilla.redhat.com/show_bug.cgi?id=1358861
https://bugzilla.redhat.com/show_bug.cgi?id=247239
https://bugzilla.redhat.com/show_bug.cgi?id=439290

Already moved to upstream tracking at least once in the Trac days (,http://rpm.org/ticket/31) only the upstream ticket system changed and old stuff got flushed. And here we go again:

$ rpm -qla | grep "(contains no files)" | wc -l
25

Such messages have no business being on stdout, but fixing this requires redesigning half of how rpm outputs information, and would break half of rpm-using scripts out there. So if changed, we should time it along with other cli-breakage so that we only break things once. Exit code sanity come to mind as a related thing.

[DemiMarie]

Exit code sanity come to mind as a related thing.

Does that include exiting with a non-zero status if an I/O error occurs?