From d0f5b69a19236ea3c17dd306708d6ece43283501 Mon Sep 17 00:00:00 2001 From: Greg Becker Date: Thu, 9 Jul 2020 13:08:51 -0500 Subject: [PATCH] installation: skip repository metadata for externals (#16954) When Spack installs a package, it stores repository package.py files for it and all of its dependencies - any package with a Spack metadata directory in its installation prefix. It turns out this was too broad: this ends up including external packages installed by Spack (e.g. installed by another Spack instance). Currently Spack doesn't store the namespace properly for such packages, so even though the package file could be fetched from the external, Spack is unable to locate it. This commit avoids the issue by skipping any attempt to locate and copy from the package repository of externals, regardless of whether they have a Spack repo directory. --- lib/spack/spack/installer.py | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/lib/spack/spack/installer.py b/lib/spack/spack/installer.py index a2b0220a8b..978296e051 100644 --- a/lib/spack/spack/installer.py +++ b/lib/spack/spack/installer.py @@ -405,9 +405,14 @@ def dump_packages(spec, path): source = spack.store.layout.build_packages_path(node) source_repo_root = os.path.join(source, node.namespace) - # There's no provenance installed for the source package. Skip it. - # User can always get something current from the builtin repo. - if not os.path.isdir(source_repo_root): + # If there's no provenance installed for the package, skip it. + # If it's external, skip it because it either: + # 1) it wasn't built with Spack, so it has no Spack metadata + # 2) it was built by another Spack instance, and we do not + # (currently) use Spack metadata to associate repos with externals + # built by other Spack instances. + # Spack can always get something current from the builtin repo. + if node.external or not os.path.isdir(source_repo_root): continue # Create a source repo and get the pkg directory out of it.