Bug 1127209 - zypper complains about --quiet --verbose cmdline option
zypper complains about --quiet --verbose cmdline option
Status: RESOLVED INVALID
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: libzypp
Current
x86-64 Linux
: P5 - None : Enhancement (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-02-27 14:13 UTC by Olaf Hering
Modified: 2019-02-27 16:04 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Hering 2019-02-27 14:13:27 UTC
My wrapper for zypper is actually called 'zypper', comes first in PATH and calls %_bindir/zypper.
Yesterday I noticed that 'zypper in v<TAB>' complains that both --quiet and --verbose are passed as cmdline, and that both contradict each other. As a result no tab completion happens.
I do not actively use TW anymore, this behavior might be in place since a while already.

In case the cmdline options are really --quiet --verbose, zypper should just tweak verbosity in the order of options. If quiet comes last, it takes effect.
Comment 1 Michael Andres 2019-02-27 16:04:07 UTC
We somewhat dislike the idea of having different policies for such cases. Either all such option sets conflict, or it's always the last one that wins. So no special solution for quiet/verbose.