Description of problem: I commonly used to use the following construct with yum: yum install -y `cat putback` where putback contained a list of packages to try to install. It would install all of the packages in the list that could be installed. With dnf if any package can't be installed (commonly because of a soname conflict), no packages get installed. Nor is there any message indicating that some could be installed, but weren't.
Hello, thank you for the report. Can you please explain on an example why would you be OK if the some of the packages will be installed and some of them won't? Would the solution proposed in https://bugzilla.redhat.com/show_bug.cgi?id=1197456#c17 work for you?
Because it is a lot easier (and faster) to have dnf install as much as it can of the set, than to issue a separate dnf install command for each package. It is similar to the implied skip broken that dnf uses when updating, dnf should do as much as it can. If you don't think it should by default, then maybe the skip broken setting should be explicitly settable again. And no, the solution in 1197456 isn't good as I would need to parse the output of dnf and run a modified command a second time to automate doing the excludes.
This is arguably a duplicate of 1197456, but the bugs are filed against different releases.
Sorry, I still don't understand what is the benefit of installing some of the packages if some of them cannot be installed. If you could explain it on an example of some real packages, maybe it would be more easily understandable.
Because you can't use packages if they aren't installed. The list of packages to be installed are ones that I removed because they are blocking the upgrade of other packages or were dropped from rawhide. I want to reinstall these packages as soon as they are fixed. In effect I don't want one big transaction, but a separate one for each listed package. However the install attempts go a lot faster when I do them in a single command rather than running a separate command for each attempted reinstall. dnf is no longer faster than yum when I end up running hundreds of dnf commands instead of a single one like I can do with yum. (This isn't really rawhide specific, but soname bump issues are a lot more common there than in releases.)
OK, I hope I understand the use case now. There is a list of packages. All of them should be installed at some moment in the future but some of the packages may not be available now so it's enough to install at least the rest of them now. So, would it be acceptable for you if it would be supported via some switch? I'm asking because YUM apparently doesn't require a switch to do that but we intentionally differ here. (It can be something like the --skip-broken switch, although I'd prefer different name, or maybe just something like --skip-unavailable switch...)
Oh, I forget that they might be available (but broken) to, so ignore the "--skip-unavailable" variant...
Some might not be available, but more likely they aren't currently installable because of dependency issues. The ones that aren't available might be obsoleted. I don't want unavailable packages blocking other packages from being installed either, even though those will likely get removed from the list at some point. The switch name might indicate best effort (short of removing or downgrading other packages).
So, I take it as a switch would be an acceptable solution for you. *** This bug has been marked as a duplicate of bug 1197456 ***