From c5adf1ff3e5738579c1da72970bc6a5014bf4c40 Mon Sep 17 00:00:00 2001 From: Eleni Mathioulaki <emathioulaki@athenarc.gr> Date: Tue, 28 Feb 2023 14:09:07 +0100 Subject: [PATCH] remove `--no-check-signature` everywhere --- .gitlab-ci.yml | 2 +- install_spack_env.sh | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 1443195b..540dd471 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -261,7 +261,7 @@ sync-gitlab-spack-instance: # There is a known spack bug (https://github.com/spack/spack/issues/29447) in installing test dependencies for installation tests. The workaround suggested # in the issue is to NOT concretize separately, but simply remove the .lock file and let the enironment be concretized by the spack install command: - rm $SPACK_ROOT/var/spack/environments/$SPACK_NFS_ENV/spack.lock || echo "No spack.lock file" - - spack install -y -j2 --fresh --no-check-signature --test root + - spack install -y -j2 --fresh --test root - spack module tcl refresh -y - spack reindex - spack env loads -r diff --git a/install_spack_env.sh b/install_spack_env.sh index 9ea0ac73..c5aaa511 100644 --- a/install_spack_env.sh +++ b/install_spack_env.sh @@ -54,7 +54,7 @@ spack env activate $EBRAINS_SPACK_ENV # remove the .lock file and let the enironment be concretized by the spack install command: rm $SPACK_ROOT/var/spack/environments/$EBRAINS_SPACK_ENV/spack.lock || echo "No spack.lock file" # install the environment, use 2 jobs to reduce the amount of required RAM -spack install -y -j2 --fresh --no-check-signature --test root +spack install -y -j2 --fresh --test root # rebuild spack's database spack reindex -- GitLab