--checksum-type does not affect the checksum used in primary.xml
Description of problem:
Setting the --checksum-type on a repo does not seem to have an effect.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a repo, perhaps the zoo repo, setting --checksum-type sha1
2. Sync & Publish
Open the primary.xml.gz file in the published repodata folder. Observe that sha256 was used. For example, I see this tag in the bear package:
<checksum pkgid="YES" type="sha256">7a831f9f90bf4d21027572cb503d20b702de8e8785b02c0397445c2e481d81b3</checksum>
I expected sha1 to have been used, since I explicitly chose sha1.
I wonder if this is because I sync'd the repo, and perhaps the upstream zoo repo used sha256 and that overrides the --checksum-type flag? I think it's a bug either way, since the --checksum-type flag helptext doesn't list any conditions on whether it gets used.
+ This bug was cloned from Bugzilla Bug #1167456 +
#3 Updated by bcourt over 6 years ago
This behavior is by design. A documentation update would probably be good however the current user guide doesn't elaborate on the --checksum-type option much at all. We do not currently recalculate the checksums for individual content units. the --checksum-type parameter is only for the metadata files that are generated as part of the repo publish.
Please register to edit this issue