Bug 1277965 - dnf upgrades list should be processed in batches of 250. REQUEST
Summary: dnf upgrades list should be processed in batches of 250. REQUEST
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf-plugin-system-upgrade
Version: 23
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-04 12:35 UTC by Leslie Satenstein
Modified: 2015-11-04 14:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-04 14:01:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1276886 0 unspecified CLOSED Downloaded packages are deleted too quickly, leading to frustration 2021-02-22 00:41:40 UTC

Internal Links: 1276886

Description Leslie Satenstein 2015-11-04 12:35:59 UTC
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:

Comment 1 Zbigniew Jędrzejewski-Szmek 2015-11-04 14:01:44 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.