Support for choosing the checksum type in updateinfo
Given errata where the package list has checksums of multiple types, pulp can publish only one of those types, and filter out any others.
When pulp generates updateinfo.xml as part of a yum publish, it has logic for choosing the checksum type(s) based on the checksum(s) in the errata metadata and the checksum type of the repo. For example, if the repo is configured for sha256 and the errata metadata includes both md5 and sha256, pulp will use sha256. For backward-compatibility reasons, it is sometimes needed to use a checksum type in updateinfo that is different than the checksum type of the repo itself. Please have a way to optionally configure a checksum type for updateinfo. When it's not set it can fall back to the checksum type of the repo.
#5 Updated by mhrivnak about 5 years ago
I assume the checksums being referred to are the rpm checksums in the package list?
Dennis, are you asking for:
- Given errata where the package list has checksums of multiple types, pulp can publish only one of those types, and filter out any others.
or are you asking for:
- Pulp can publish an erratum using any supported checksum type. If publish is requested with a checksum type where those values are not already in the package list for any given erratum, pulp will go find the relevant RPMs in the database (assuming they are in the repo), and retrieve the checksums.
The former is easy. The latter is complex. An Errata unit in pulp does not have a direct association with RPMs, so retrieving a checksum value would require a unit search by nevra within the repo for each RPM. That could obviously add substantial time if there are many errata.
And if you want the latter, is md5 a checksum type we would need to support retrieval for? We have only been planning to store sha1 and sha256 checksums on RPM units.
Please register to edit this issue