Skip to content

common-api-v2/gadi/packages.yaml: externals are treated as concrete specs#99

Merged
harshula merged 2 commits intomainfrom
development
Feb 6, 2026
Merged

common-api-v2/gadi/packages.yaml: externals are treated as concrete specs#99
harshula merged 2 commits intomainfrom
development

Conversation

@harshula
Copy link
Copy Markdown
Collaborator

@harshula harshula commented Feb 6, 2026

…pecs

* As of spack/spack#51118 we need to accommodate:
  "To be backward compatible with external specs specifying a compiler, for
   instance mpich %gcc@9, Spack will match the compiler specification to an
   existing external. It will fail when the specification is ambiguous, or
   if it does not match any other externals."
@harshula
Copy link
Copy Markdown
Collaborator Author

harshula commented Feb 6, 2026

Testing

$ git -C spack-config branch
* development
  main

$ git -C spack-config log
commit fcfa1517372adfb36370e6de433a2d7a3a074b27 (HEAD -> development, origin/development)
Author: Harshula Jayasuriya <[email protected]>
Date:   Fri Nov 28 01:13:54 2025 +1100

    common-api-v2/gadi/packages.yaml: test if this works

commit e070b4e988bf53d2e2b9563db60e955e778cbe48 (origin/development-gadi)
Author: Harshula Jayasuriya <[email protected]>
Date:   Sun Nov 23 23:57:26 2025 +1100

    common-api-v2/gadi/packages.yaml: externals are treated as concrete specs
    
    * As of https://github.com/spack/spack/pull/51118 we need to accommodate:
      "To be backward compatible with external specs specifying a compiler, for
       instance mpich %gcc@9, Spack will match the compiler specification to an
       existing external. It will fail when the specification is ambiguous, or
       if it does not match any other externals."
$ spack find
==> In environment /g/data/tm70/hj1810/test-v1.1.1-2/ACCESS-OM2
==> 1 root specs
-- no arch / no compilers ---------------------------------------
[+] [email protected]=latest

-- linux-rocky8-x86_64 / %c,cxx,[email protected] ---------
[email protected]=mom5  [email protected]

-- linux-rocky8-x86_64 / %c,[email protected] -----------------
[email protected]  [email protected]    [email protected]
[email protected]    [email protected]  [email protected]

-- linux-rocky8-x86_64 / %c,[email protected] -------------
[email protected]          [email protected]
[email protected]=access-om2  [email protected]=2025.03.001
[email protected]=access-om2

-- linux-rocky8-x86_64 / %[email protected] ---------------------
[email protected]     [email protected]  [email protected]   [email protected]
[email protected]  [email protected]  [email protected]

-- linux-rocky8-x86_64 / %[email protected] ---------------
[email protected]  [email protected]
[email protected]              [email protected]=access-om2

-- linux-rocky8-x86_64 / no compilers ---------------------------
[email protected]=latest  [email protected]
[email protected]                       [email protected]
[email protected]               [email protected]
==> 30 installed packages
==> 0 concretized packages to be installed (show with `spack find -c`)

@harshula harshula merged commit 567b698 into main Feb 6, 2026
@github-project-automation github-project-automation bot moved this from New Issues 🌅 to Done ✅ in Model Release Feb 6, 2026
harshula added a commit that referenced this pull request Feb 6, 2026
…#99)

* As of spack/spack#51118 we need to accommodate:
  "To be backward compatible with external specs specifying a compiler, for
   instance mpich %gcc@9, Spack will match the compiler specification to an
   existing external. It will fail when the specification is ambiguous, or
   if it does not match any other externals."
* We can no longer specify only the compiler name. If we specify the compiler
  name, then we must include a compiler version.
harshula added a commit that referenced this pull request Feb 6, 2026
…#99)

* As of spack/spack#51118 we need to accommodate:
  "To be backward compatible with external specs specifying a compiler, for
   instance mpich %gcc@9, Spack will match the compiler specification to an
   existing external. It will fail when the specification is ambiguous, or
   if it does not match any other externals."
* We can no longer specify only the compiler name. If we specify the
  compiler name, then we must include a compiler version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done ✅

Development

Successfully merging this pull request may close these issues.

2 participants