Commit 62f1c71e authored by Holger Levsen's avatar Holger Levsen

reproducible Archlinux: add comment explaining why we (rarely) might delete…

reproducible Archlinux: add comment explaining why we (rarely) might delete packages which are building
Signed-off-by: Holger Levsen's avatarHolger Levsen <holger@layer-acht.org>
parent 3d88820d
......@@ -319,7 +319,6 @@ See link:https://jenkins.debian.net/userContent/about.html["about jenkins.debian
* use db - see https://tests.reproducible-builds.org/reproducibledb.html
** scheduler.sh:
*** dont delete packages which are building?
*** use asp to update trunk packages?
** html:
*** leave all pkg.html files, delete them (much) later, then check all pkg.* files are gone
......
......@@ -59,6 +59,10 @@ update_archlinux_repositories() {
for i in $(find $BASE/archlinux/$REPO -type d -wholename "$BASE/archlinux/$REPO/*" | sort) ; do
PKG=$(basename $i)
if ! grep -q "$REPO $PKG" ${ARCHLINUX_PKGS}_full_pkgbase_list > /dev/null ; then
# we could check here whether a package is currently building,
# and if so defer the pkg removal. (but I think this is pointless,
# as we are unlikely to kill that build, so meh, let it finish
# and fail to update the db, because the package is gone...)
let REMOVED=$REMOVED+1
REMOVE_LIST="$REMOVE_LIST $REPO/$PKG"
rm -r --one-file-system $BASE/archlinux/$REPO/$PKG
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment