On Sun, Jun 24, 2012 at 02:22:06AM +0900, Osamu Aoki wrote: > So you mean --quiet and error exit is good? I see. I still worry about > being too quiet to hide source of the trouble. Do you think we need
As far as I can see --quiet never hides error conditions. After all --quiet is not that quiet. It suppresses the "Updating the super catalog..." and it suppresses warnings about leftover or broken package catalogs. So whenever the exit code is non-zero there will be some (die) message. > update-catalog --quiet --update-super || update-catalog --update-super > > If --quiet gives good enough indication of error, we do not need this. I > have not checked.... Maybe I am too worried with no reason. If you > think this is OK, no problem with me. As laid out above and as can be seen by searching update-catalog for '$quiet' the --quiet switch never suppresses messages for failures that result in a non-zero exit. So your proposed solution just prints the error twice (assuming idempotency) plus some additional messages. > > What kind of failures are "normal errors"? Which failures would you like > > not to be loud? > I have no idea. That is why I marked FYI. Maybe non-essential > variation. Unless you can answer the questions above, I see little point in changing the current --quiet behaviour. So thanks for having a look even though the issue turned out to be a non-issue thus far. It might well have been one. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
