Project

Profile

Help

Story #3956

on_demand repositories should not allow custom checksum values

Added by jsherril@redhat.com about 3 years ago. Updated over 2 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

on_demand repositories should always use the same checksums as their upstream repositories. It doesn't make sense to set a custom checksum on those repos.

History

#1 Updated by ttereshc about 3 years ago

To cover switching from immediate to on_demand and back, I suggest to not touch and preserve the existing custom checksum but in case of on_demand policy always use the upstream one.
Thoughts?

#2 Updated by daviddavis about 3 years ago

  • Tracker changed from Issue to Story
  • % Done set to 0

ttereshc, I think that makes sense.

Also, converting this issue to a story per our triage today.

#3 Updated by bmbouter over 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

#4 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF