index : builder | |
Archlinux32 build system | gitolite user |
summaryrefslogtreecommitdiff |
author | Erich Eckner <git@eckner.net> | 2020-02-20 13:47:22 +0100 |
---|---|---|
committer | Erich Eckner <git@eckner.net> | 2020-02-20 13:47:22 +0100 |
commit | 6381d1866fa9303fce0d38ee2ce7b589e9b3e28c (patch) | |
tree | a5e9b6075778f9aa699e4ff5541b2cd8e2225d5c | |
parent | 7d1f4ce19d470f0e659f503165beaa0cd133ed9f (diff) |
-rwxr-xr-x | bin/seed-build-list | 6 |
diff --git a/bin/seed-build-list b/bin/seed-build-list index 32bd6df..2d840db 100755 --- a/bin/seed-build-list +++ b/bin/seed-build-list @@ -727,10 +727,10 @@ if ${update}; then # TODO: We might now need to delete deletion-list packages which are now # on the build-list, too. The questions are: -# Does that actually happen? -# Why should that actually happen? +# Does that actually happen? Yes, it does! +# Why should that actually happen? Because we requested to reschedule them! # Should we rather fix the other end (e.g. should these packages really -# be on the build-list)? +# be on the build-list)? Yes, if they were wrongly on the deletion-list! } | \ mysql_run_query |