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

Create publish_upstream_release_fields repo/publication option #793

Closed
quba42 opened this issue Jun 6, 2023 · 0 comments · Fixed by #794
Closed

Create publish_upstream_release_fields repo/publication option #793

quba42 opened this issue Jun 6, 2023 · 0 comments · Fixed by #794
Labels
.feature CHANGES/<issue_number>.feature

Comments

@quba42
Copy link
Collaborator

quba42 commented Jun 6, 2023

The idea is to make the new behaviour from #782 opt-in on the publication side.

That way we can prevent new syncs + publish in existing repos from suddenly changing the release file fields post pulp_deb upgrade.

This would be undesirable since it requires all APT clients consuming the publication to confirm that the changed release file fields are acceptable.

Therefore existing repos should initially be seeded with publish_upstream_release_fields = False while the default value for new repos should be True.

@quba42 quba42 added Triage-Needed .feature CHANGES/<issue_number>.feature and removed Triage-Needed labels Jun 6, 2023
hstct pushed a commit to ATIX-AG/pulp_deb that referenced this issue Jun 7, 2023
hstct pushed a commit to ATIX-AG/pulp_deb that referenced this issue Jun 7, 2023
hstct pushed a commit to ATIX-AG/pulp_deb that referenced this issue Jun 20, 2023
hstct pushed a commit to ATIX-AG/pulp_deb that referenced this issue Jun 20, 2023
hstct pushed a commit to ATIX-AG/pulp_deb that referenced this issue Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
.feature CHANGES/<issue_number>.feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant