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): 2.4.3-1 How reproducible: Every time Steps to Reproduce: 1. Create a repo, perhaps the zoo repo, setting --checksum-type sha1 2. Sync & Publish Actual results: 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> Expected results: I expected sha1 to have been used, since I explicitly chose sha1. Additional info: 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.
I tried creating repos without feeds and uploading packages to them with the --checksum-type set to "sha", but the primary.xml still shows sha256 as the checksum type used.
This behavior should be documented in the help-text and docs. It should note that checksum types can be set in multiple places. ie: upload, repo create, etc.
Moved to https://pulp.plan.io/issues/627