Add tests to ensure all control file fields present in an upstream package index will be present in pulp_deb
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 71
- Forks
- 91
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 22
Description
Author: @quba42 (quba42)
Redmine Issue: 7266, https://pulp.plan.io/issues/7266
We should have test packages/assertions etc. to ensure that each control file field present in an upstream repo makes it into our published repos.
Should be ensured for both simple and structured publish.
Note that "Description-md5" and "Build-Essential" are pure metadata fields that may be present in (upstream) Package indices but are not present in the package control files.
We are ignoring such fields for now.
Any attempt to support them would be a new feature.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the existing package and assertion test helpers, then find the tests for simple and structured publishing. Compare fields in an upstream Package index with the published pulp_deb output, excluding Description-md5 and Build-Essential. Done means both publish modes have coverage confirming supported control fields are preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100