Bug 2058477 - Failed Delta RPMs increased 372.7 MB of updates to 444.2 MB (16.1% wasted)
Summary: Failed Delta RPMs increased 372.7 MB of updates to 444.2 MB (16.1% wasted)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: deltarpm
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Blaha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-25 05:42 UTC by cornel panceac
Modified: 2022-12-13 16:47 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-13 16:47:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description cornel panceac 2022-02-25 05:42:39 UTC
Description of problem:
Delta RPM sometimes dereases the download by a few hundred KB for a hundred megabytes download (Around 0.01% improve, at the expense of additional CPU power). But some other times it makes things worse, due to failed delta RPMs.
How can delta RPMs be disabled?

Version-Release number of selected component (if applicable):
any

How reproducible:
depends on chance.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Marek Blaha 2022-02-25 06:59:56 UTC
Two options:

- disable delta rpm in /etc/dnf/dnf.conf by adding `deltarpm=0` - see man dnf.conf

- uninstall deltarpm package

Comment 2 cornel panceac 2022-03-06 11:28:17 UTC
Thank you Marek.
Re-assigning to deltarpm. 
The problem is: deltarpm is not working as expected, and the fix should be distribution-wide, in my opinion, instead of each affected user doing one the above two things.
What's your opinion?

Comment 3 Marek Blaha 2022-03-07 07:32:17 UTC
To be honest, I only answered the question how delta rpm could be disabled.
I did some investigation and it looks like there is a bug causing deltarpm to fail - https://bugzilla.redhat.com/show_bug.cgi?id=1873876
This bug might be a duplicate of the mentioned one, but without more information it's hard to tell.

Comment 4 Ben Cotton 2022-11-29 17:57:52 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Ben Cotton 2022-12-13 16:47:04 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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