Skip to content

RPMs metadata V2#205

Merged
lubomir merged 2 commits intorelease-engineering:developmentfrom
guillermodotn:metadata-rpms
Feb 19, 2026
Merged

RPMs metadata V2#205
lubomir merged 2 commits intorelease-engineering:developmentfrom
guillermodotn:metadata-rpms

Conversation

@guillermodotn
Copy link
Contributor

  • Update Rpms.add() to accept Location objects
  • Implement v2.0 serialization for all metadata classes (images, rpms done)
  • Implement v2.0 deserialization for all metadata classes (images, rpms done)
  • Support v1.2 serialization/deserialization (backward compat) (images, rpms done)
  • Write unit tests for each metadata class (images, rpms done)

Copy link
Contributor

@lubomir lubomir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

I'm kinda curious how much it's going to increase the size of the file, but that is likely a cost we need to pay anyway.

One potential improvement not related to distributed data is the sigkey. The metadata can only represent a single key, but in rpm v6 can be signed with multiple keys. But that is a separate concern not related to this specific effort.

@lubomir lubomir merged commit 4fcde10 into release-engineering:development Feb 19, 2026
10 checks passed
@guillermodotn
Copy link
Contributor Author

I estimate up to 3x depending of the local path to remote/OCI ratio of the file.


One potential improvement not related to distributed data is the sigkey. The metadata can only represent a single key, but in rpm v6 can be signed with multiple keys. But that is a separate concern not related to this specific effort.

GTK

@guillermodotn guillermodotn deleted the metadata-rpms branch March 4, 2026 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants