bin/get-package-updates: revert 1aa4e18a3336e2d16f73089277f749fc3f9a3147

* packages on the deletion-list should not be scheduled over and over again
* only if a newer version of that package is available upstream, we should re-consider it
* if there is no newer version, we should not consider it for the build list
* because considering it for the build-list triggers `makepkg --printsrcinfo`, which makes get-package-updates slow, if we have many black-listed packages (which we have)

1 files changed, 1 insertions, 5 deletions

diff --git a/bin/get-package-updates b/bin/get-package-updates
index 738046d..60879f3 100755
--- a/bin/get-package-updates
+++ b/bin/get-package-updates
@@ -302,15 +302,11 @@ echo 'Check modified packages from the last update, and put them to the build li
   )
   # shellcheck disable=SC2016
   {
-    printf 'SELECT DISTINCT `package_sources`.`pkgbase`,'
+    printf 'SELECT `package_sources`.`pkgbase`,'
     printf '`package_sources`.`git_revision`,'
     printf '`upstream_repositories`.`name`'
     printf ' FROM `package_sources`'
     mysql_join_package_sources_upstream_repositories
-    mysql_join_package_sources_build_assignments
-    mysql_join_build_assignments_binary_packages
-    mysql_join_binary_packages_binary_packages_in_repositories
-    printf ' AND NOT `binary_packages_in_repositories`.`is_to_be_deleted`'
   } \
   | mysql_run_query \
   | tr '\t' ' ' \