path: root/bin/return-assignment
diff options
authorErich Eckner <>2020-02-13 11:14:33 +0100
committerErich Eckner <>2020-02-13 11:14:33 +0100
commitbf1255563787a2554265d5728d807ea91acec5a0 (patch)
tree0aadd669555163cd48c008a1f354a732afd5ebe2 /bin/return-assignment
parent47c8a23cf8e71b44adcddddba6bba2ae32c33726 (diff)
bin/return-assignment: remove done TODO
Diffstat (limited to 'bin/return-assignment')
1 files changed, 0 insertions, 8 deletions
diff --git a/bin/return-assignment b/bin/return-assignment
index ba08a18..e24afa6 100755
--- a/bin/return-assignment
+++ b/bin/return-assignment
@@ -19,14 +19,6 @@
# 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