From 68df3b54a3335f6639dc269f879b60d13cd14cbc Mon Sep 17 00:00:00 2001 From: Erich Eckner Date: Wed, 12 Feb 2020 21:58:15 +0100 Subject: bin/return-assignment: add TODO describing the current package-vanish-problem --- bin/return-assignment | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/bin/return-assignment b/bin/return-assignment index e24afa6..ba08a18 100755 --- a/bin/return-assignment +++ b/bin/return-assignment @@ -19,6 +19,14 @@ # TODO: remove hard-coded package suffixes +# TODO: Vanishing packages are split packages, where one part is on the +# deletion-list and one is in a regular package. Someone sees the +# deletion-list package and deletes *both* (same build_assignment) +# without removing the real package from the mirror. Questions: 1. Do we +# want to have a package on the deletion-list and in a repository in the +# first place? 2. What should happen, should one decide to delete the +# deletion-list package? + # shellcheck disable=SC2119,SC2120 # shellcheck source=../lib/load-configuration -- cgit v1.2.3-70-g09d2