Description of problem: dnf should exit immediately if an option is given that does not exist. This does the right thing: # dnf -a as does this: # dnf -a upgrade This does not work: # dnf upgrade -a Using metadata from Wed Apr 15 14:35:15 2015 No match for argument: -a Error: No packages marked for upgrade. nor does this: # dnf list -z Version-Release number of selected component (if applicable): dnf-0.6.4-1.fc21.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hello, thank you for the report. Actually, this is something that you should expect because according to the man pages, the synopsis is "dnf [options] <command> [<args>...]". So, anything passed after a "<command>" should be handled as an argument of the command. So, if we are going to officially support putting global options after the "<command>", we should document it as well.
Yes I understand that, but if an invalid option is passed, you want dnf to exit.
*** Bug 1233845 has been marked as a duplicate of this bug. ***
(In reply to James Patterson from comment #2) > Yes I understand that, but if an invalid option is passed, you want dnf to > exit. Which is basically what every other Linux program does. Including yum BTW.
Will be fixed along with argparsing DNF refactoring.
Any idea of the time frame?
Fixed as a part of DNF 2.0 argument parser rewrite https://github.com/rpm-software-management/dnf/pull/474
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
as Michael said.