Project

Profile

Help

Issue #627

closed

--checksum-type does not affect the checksum used in primary.xml

Added by rbarlow over 9 years ago. Updated over 5 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.4.0
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

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.

+ This bug was cloned from Bugzilla Bug #1167456 +


Related issues

Is duplicate of RPM Support - Issue #1618: --checksum-type is brokenCLOSED - CURRENTRELEASEmhrivnakActions

Also available in: Atom PDF