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.

Sign up for GitHub

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

Jump to bottom

Repo versions not created via sync should not be verbatim published #720

Open
quba42 opened this issue Feb 13, 2023 · 1 comment
Open

Repo versions not created via sync should not be verbatim published #720

quba42 opened this issue Feb 13, 2023 · 1 comment
Labels
.feature CHANGES/<issue_number>.feature

Comments

@quba42
Copy link
Collaborator

quba42 commented Feb 13, 2023

The verbatim publisher should do some sanity checking, and refuse to run for repo versions that cannot be meaningfully verbatim published. Right now this is possible (will run successfully), but won't create a publication with metadata (i.e. a publication that cannot be consumed by an APT client).
@quba42
Copy link
Collaborator Author

quba42 commented Aug 23, 2023

Somewhat related issue: https://discourse.pulpproject.org/t/rfc-separating-sync-and-upload-workflows-in-pulp-deb-and-others/787

The common denominator is: "don't allow the user to shoot themselves in the foot by combining incompatible workflows"

@quba42 quba42 added the .feature CHANGES/<issue_number>.feature label Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
.feature CHANGES/<issue_number>.feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@quba42