Description of problem: I ran the dnf upgrade to go from Fedora 22 to Fedora 23 and dnf had 4412 entries in its download list. dnf attempts to download all 4412 before performing the upgrade. If there is a network failure or other failure, dnf must restart. It does appear to continue, as does an update. Request dnf upgrade be reworked so that it does sub batches of 250 updates. This change would allow one group of 250 upgrades to be processed before the next group is done. As an aside. When a dnf update has too many entries, I batch the updates by taking a* through j*, k* through p*, and then the rest. Version-Release number of selected component (if applicable): 1.1.3+ How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
system-upgrade should not require re-downloading stuff after a network failure. It it does that, we'll have to fix it. There's already an open bug about re-downloading: 1276886. This is much more complicated than it might seem. In general it is not possible to always split the transaction, and one of the main advantages of using system-upgrade is that it does the full upgrade in one step, so you are not left with a partially upgraded system. Sorry, this is not an option.