[Rpm-maint] [rpm-software-management/rpm] Discussion: Understanding the Ecosystem Impact of RPM v6 on Repository Metadata and Client Behavior (Discussion #3968)

[Shashank Taliwal]

Hello everyone,

As suggested on the RPM v6 announcement thread, I'm opening a new discussion to explore the downstream effects of the new package format on the wider ecosystem.

I want to start by thanking the team for the clarification that the core RPM project doesn't directly manage repository metadata. We understand that this is handled by separate tools like createrepo_c and consumed by clients like dnf. This discussion is aimed at bringing together expertise from all parts of that ecosystem to understand the full picture.

>From the perspective of those who develop and maintain repository management infrastructure (like Jfrog Artifactory), our goal is to ensure seamless support for v6 packages. To that end, we'd like to ask the broader community for insights on the following topics:

1. **Impact on Repository Metadata (repodata) Generation**
Since the v6 package format contains new features like multiple signatures, stronger checksums, and 64-bit fields, how are these expected to be represented in the repository metadata files (primary.xml.gz, filelists.xml.gz, etc.)? Are there anticipated changes or extensions to the schemas of these files?

2. **Expected Client Behavior and Compatibility**
What is the intended behavior for clients in this new ecosystem?

How will modern clients (e.g., based on libdnf5) handle repositories that contain a mix of v4 and v6 packages?

What is the expected failure mode for an older, v6-unaware client that tries to read a repodata directory containing metadata from v6 packages? Will it error out, or gracefully ignore what it can't parse?

3. **Guidance for Tooling Developers**
For those of us in the community developing tools that need to proxy, cache, and sometimes generate repository metadata, what would be the best approach to ensure a smooth transition? Is there a recommended place to follow the evolution of the repository format and best practices for v6 compatibility?

We welcome any insights, pointers, or discussion from developers of createrepo_c, dnf/yum, distribution maintainers, and anyone else with expertise in this area.

Thank you!

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/3968
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/repo-discussions/3968 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20250925/39034b39/attachment.htm>