diff options
author | Erich Eckner <git@eckner.net> | 2020-02-12 21:58:15 +0100 |
---|---|---|
committer | Erich Eckner <git@eckner.net> | 2020-02-12 21:58:15 +0100 |
commit | 68df3b54a3335f6639dc269f879b60d13cd14cbc (patch) | |
tree | 07a63630e7dc16a06ee800319107e0d946ddc868 /bin | |
parent | e03b01a22cabc8bb77b7cc09916b9a2908f18453 (diff) | |
download | builder-68df3b54a3335f6639dc269f879b60d13cd14cbc.tar.xz |
bin/return-assignment: add TODO describing the current package-vanish-problem
Diffstat (limited to 'bin')
-rwxr-xr-x | bin/return-assignment | 8 |
1 files changed, 8 insertions, 0 deletions
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 |