Hide Forgot
Description of problem: If just one package of the list does not exist nothing happens. But I may want to install the other ones. Version-Release number of selected component (if applicable): dnf-1.1.8-1.fc25.noarch How reproducible: Always. Steps to Reproduce: dnf install gnome-terminal FOOBAR Actual results: Last metadata expiration check: 2:31:47 ago on Thu Apr 14 14:47:37 2016. No package FOOBAR available. Error: Unable to find a match. Expected results: No package FOOBAR available. Installing: gnome-terminal-3.20.1-1.fc25.x86_64 OR: No package FOOBAR available. To install the remaining specified packages use: --ignore-missing-packages Additional info: Maybe some --ignore-missing-packages exists but I do not see it in dnf install --help and also 'dnf install' could suggest it when some of its arguments did exist + they were not installed.
dnf install --setopt strict=false gnome-terminal FOOBAR is what you are looking for.
Yes, thanks. I do not know why it is not the default. At least yum (RHEL-7) behaved that way and this is what I expect as a user. But if strict=true needs to be the default please suggest '--setopt strict=false' while printing the final error message (if some of dnf install arguments did exist + they were not installed). I had to do instead: for i in `cat ~/INSTALL`;do dnf install $i;done
It isn't a default because dnf prefers consistent behaviour across commands. So both dnf install A dnf install A B fail if A can't be installed, For people who'd like to stick with yum's behaviour there's strict=false option.
(In reply to Michael Mráka from comment #3) > It isn't a default because dnf prefers consistent behaviour across commands. One could say consistency means that if B is installable and B is requested then B should get installed. But sure that's DNF's decision. (In reply to Jan Kratochvil from comment #2) > But if strict=true needs to be the default please suggest '--setopt > strict=false' while printing the final error message (if some of dnf install > arguments did exist + they were not installed). This possible fix has not been addressed. If it is not going to be addressed then the resolution should be CLOSED-WONTFIX (not CLOSED-NOTABUG).