| Line 152: | Line 152: | ||
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | ||
--> | --> | ||
The only noticeable effect should be smaller metadata thanks to zstd compression resulting in faster downloads (when zchunk is not used). The (de)compression speed up is not very noticeable. | |||
For example for Fedora 37: | |||
primary.xml.gz: 6.1M -> primary.xml.zst: 5.0M | |||
filelists.xml.gz: 22M -> filelists.xml.zst: 17M | |||
other.xml.gz: 2.4M -> other.xml.zst: 1.8M | |||
== Dependencies == | == Dependencies == | ||
Revision as of 08:48, 8 March 2023
createrepo_c 1.0.0
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
Update createrepo_c to 1.0.0, new release will include change of default compression to zstd, no longer generating metadata in sqlite database format by default and simplified comps xml type in repodata.
Owner
- Name: Aleš Matěj
- Email: amatej@redhat.com
Current status
- Targeted release: Fedora Linux 39
- Last updated: 2023-03-08
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
- Switch default compression from gz to zstd. DNF is able to decompress zstd via libsolv (from 0.7.0) since Fedora 30. Further information: https://github.com/rpm-software-management/createrepo_c/issues/82.
- Stop generating metadata in sqlite database format by default. It will still be possible to create them using a --database switch or via sqliterepo_c tool. (It looks like the only user left is mdapi: https://github.com/fedora-infra/mdapi/issues/97). Further information: https://github.com/rpm-software-management/createrepo_c/issues/338 and https://pagure.io/releng/issue/10745
- When adding groups.xml to repodata createrepo_c currently adds two variants to repomd.xml. The specified file as is, uncompressed, with the type "group" and also a compressed variant with type "group_XX", where XX is compression suffix. This is atypical and unexpected. We propose to include just one variant of groups.xml using specified compression and repomd.xml type "group". Further information: https://bugzilla.redhat.com/show_bug.cgi?id=2056318
- To reflect API and overall stability increase major version above 0.
Feedback
Benefit to Fedora
- Using zstd compression provides smaller metadata that are faster to decompress.
- Generating sqlite metadata is expensive, its slowing createrepo_c runs and it takes up space on mirrors. (For F37 updates repo: primary_db: 12.8 mb, filelists_db: 22.0 mb, other_db: 4.2 mb.)
- More consistent metadata.
Scope
- Proposal owners: Implement specified changes, mostly changes of default.
- Other developers: There are no requirements on other developers.
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
No upgrade or compatibility impact.
How To Test
Repositories generated with updated createrepo_c have to work with dnf. Specifically we should ensure that groups are still loaded.
User Experience
The only noticeable effect should be smaller metadata thanks to zstd compression resulting in faster downloads (when zchunk is not used). The (de)compression speed up is not very noticeable. For example for Fedora 37: primary.xml.gz: 6.1M -> primary.xml.zst: 5.0M filelists.xml.gz: 22M -> filelists.xml.zst: 17M other.xml.gz: 2.4M -> other.xml.zst: 1.8M
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)