Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tests to ensure all control file fields present in an upstream package index will be present in pulp_deb #388

Open
pulpbot opened this issue Jan 4, 2022 · 5 comments

Comments

@pulpbot
Copy link
Member

pulpbot commented Jan 4, 2022

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.

@pulpbot pulpbot added this to the Testing milestone Jan 4, 2022
@pulpbot
Copy link
Member Author

pulpbot commented Jan 4, 2022

From: @quba42 (quba42)
Date: 2020-08-04T07:04:30Z


Note: This issue essentially adds test coverage for the fixes for https://pulp.plan.io/issues/7190.

It serves as a follow on issue, so these essential fixes can be merged without waiting for test coverage for now.

@pulpbot
Copy link
Member Author

pulpbot commented Jan 4, 2022

From: @quba42 (quba42)
Date: 2020-08-26T08:41:33Z


Clarification: This relates to APT publications.

(Verbatim publications must necessarily guarantee this already, so we do not need a test for them).

@pulpbot
Copy link
Member Author

pulpbot commented Jan 4, 2022

From: pulpbot (pulpbot)
Date: 2020-08-27T14:18:47Z


PR: #203

@quba42 quba42 removed Issue labels Jan 31, 2022
@stale
Copy link

stale bot commented May 25, 2022

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

@stale stale bot added the stale label May 25, 2022
@quba42 quba42 added the Tests label Jun 20, 2023
@stale
Copy link

stale bot commented Jun 20, 2023

This issue is no longer marked for closure.

@stale stale bot removed the stale label Jun 20, 2023
@quba42 quba42 removed this from the Testing milestone Jun 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants