We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
publish_upstream_release_fields = False
True
The text was updated successfully, but these errors were encountered:
Add publish_upstream_release_fields option
4545d55
closes pulp#793
77137b7
58fd9f4
63f7b40
eff905d
Successfully merging a pull request may close this issue.
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 beTrue
.The text was updated successfully, but these errors were encountered: