Comment 3 for bug 874409

Your reply doesn't actually help. This is a clear bug. It's either a docs bug (in which case the documentation should clearly state that progress information, such as while file is being read, cannot be silenced without silencing the entire program); or the program doesn't behave the way the documentation describes. As a user reading those docs, what I'm looking for when I go looking for a "quiet" option is a way to make the program output less verbose. In the above sample output, all most uses of the tool require (and certainly the only relevant output to the request, given that I've requested a quiet execution) is that the package is already installed.

Local definitions of what a "progress" message vs. and "error" message are isn't interesting to the user. What's interesting is the result of the command, which as far as I can tell is either the second-to-last line or the last two lines.

If you're set in calling only marching progress percentages "progress indications" then define a term in the documentation for "file progress messages" and create a -q level that squelches those (e.g. -q=2 becomes that and -q=3 becomes silent mode).

Either way, the docs are misleading right now.