Actions
Bug #16559
closed
checksum changes not propagated to new content view publishes
Status:
Closed
Priority:
Normal
Assignee:
Category:
Content Views
Target version:
Difficulty:
easy
Triaged:
Bugzilla link:
Pull request:
Description
1. Create a repo, set its checksum to sha256
2. create a content view with the repo added
3 Create a filter to filter out 1 package from the repo
4. Publish the content view
5. Change the repo to sha1
6. Republish the content view
check the content view to ensure that the repo in the content view was published with sha1
Updated by 
Updated by
Actions