Review behaviour when publishing empty repositories.
The current behaviour when publishing an empty repository (containing no packages) is for the pulp task to succeed without publishing anything.
We may want to review and improve this behaviour. Ideally, publishing an empty repository should create something that apt won't choke on.
Another possible use case is to ensure that pulp to pulp synchronization won't lead to a failed task.
While we are at it we may also want to consider whether there should be some kind of warning or error if an empty repository results from bad user input. The way things are now, if the user attempts to synchronize an upstream repository using for example bogus components, this will result in a successful sync with an empty repository. This may be counter intuitive for the user who has no indication what he did wrong.
#4 Updated by email@example.com over 1 year ago
- Status changed from POST to MODIFIED
- Platform Release set to 2.21.1
Please register to edit this issue