Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid tag in spack.yaml #14

Open
manodeep opened this issue Dec 19, 2024 · 0 comments
Open

Invalid tag in spack.yaml #14

manodeep opened this issue Dec 19, 2024 · 0 comments

Comments

@manodeep
Copy link

The spack.yaml specifies the tag 2024.11.15 but no such tag exists in the repo. The list of existing tags are:

[/g/data/tm70/ms2335/spack/0.22/ACCESS-TEST @gadi05] git tag
2024.09.20
2024.09.21
2024.11.0
2024.11.12

A fix would be to change the two instances of the tag to an existing one in the repo, say the previous value of 2024.11.12 (the tag value was changed in this commit).

[test] [/g/data/tm70/ms2335/spack/0.22 @gadi06] cd ACCESS-TEST/
[test] [/g/data/tm70/ms2335/spack/0.22/ACCESS-TEST @gadi06] git diff
diff --git a/spack.yaml b/spack.yaml
index c52c5f6..b12ccf8 100644
--- a/spack.yaml
+++ b/spack.yaml
@@ -4,7 +4,7 @@
 # configuration settings.
 spack:
   specs:
-    - [email protected]
+    - [email protected]
   packages:
     oasis3-mct:
       require:
@@ -34,5 +34,5 @@ spack:
           - access-test
           - oasis3-mct
         projections:
-          access-test: '{name}/2024.11.15'
+          access-test: '{name}/2024.11.12'
           oasis3-mct: '{name}/2023.11.09-{hash:7}'
[test] [/g/data/tm70/ms2335/spack/0.22/ACCESS-TEST @gadi06] 

The work should be done in conjunction with this issue on ACCESS-HIVE, which would require the tag to be set to 2024.09.20 (and not 2024.11.12) to be consistent with the image on the ACCESS-HIVE doc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant