Bug 2169377 - Do not ship zchunk metadata for fedora repository that is never updated
Summary: Do not ship zchunk metadata for fedora repository that is never updated
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pungi
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomír Sedlář
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-13 13:23 UTC by Jaroslav Mracek
Modified: 2024-11-27 21:04 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 21:04:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Mracek 2023-02-13 13:23:16 UTC
Description of problem:
zchunk metadata type is a perfect way to optimize downloads for updated metadata where only modified parts are downloaded. But the format is bigger than standard GZ compress metadata because it contains additional checksums.  It make no sense to generate such a metadata for a repository that is never updated like fedora repository.

DNF does not know the future of any repository therefore it always download zchunk metadata if they are available. The consequence - bigger mirrors, more download required and it uses more disk space with no benefit - only the same setting is used by distribution to generate `fedora` and `updates` repositories.

I propose to not generate zchunk metadata

Comment 1 Kevin Fenzi 2023-02-13 17:01:26 UTC
I think this is a completely reasonable idea... perhaps pungi could not do zchunk on 'final' releases?

Moving to pungi for comment...

Comment 2 Lubomír Sedlář 2023-02-14 08:27:03 UTC
The idea definitely makes a lot of sense. If the RC compose is not updated at any point, zchunk metadata is just taking space.

That being said, I'm not sure Pungi can reasonably stop generating it. Pungi doesn't really know what it's creating here. The way how it's configured is that there is a generic `createrepo_extra_args` option set to value `["--zck", "--zck-dict-dir=/usr/share/fedora-repo-zdicts/rawhide"]`. This gets used in the createrepo_c command.

Would it be possible to remove this option when config is prepared for the RC?

Comment 3 Fedora Release Engineering 2023-08-16 07:06:50 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 4 Aoife Moloney 2024-11-08 10:46:16 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
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 '39'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 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 Aoife Moloney 2024-11-27 21:04:35 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 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.