Final documentation updates for release 1.4.0, replace spack release …

…branch with spack tag (#612)

* Final documentation updates for release 1.4.0

* Replace spack release branch with final tag

.gitmodules

@@ -3,8 +3,7 @@
   #url = https://github.com/spack/spack
   #branch = develop
   url = https://github.com/jcsda/spack
-  # to be replaced by final tag
-  branch = release/1.4.0
+  branch = spack-stack-1.4.0
 [submodule "doc/CMakeModules"]
   path = doc/CMakeModules
   url = https://github.com/noaa-emc/cmakemodules

configs/containers/docker-ubuntu-clang-mpich.yaml

@@ -105,8 +105,7 @@ spack:
       os: ubuntu:20.04
       spack:
         url: https://github.com/jcsda/spack
-        # to be replaced by final tag
-        ref: release/1.4.0
+        ref: spack-stack-1.4.0
         resolve_sha: false
 
     # Whether or not to strip binaries

configs/containers/docker-ubuntu-gcc-openmpi.yaml

@@ -92,8 +92,7 @@ spack:
       os: ubuntu:20.04
       spack:
         url: https://github.com/jcsda/spack
-        # to be replaced by final tag
-        ref: release/1.4.0
+        ref: spack-stack-1.4.0
         resolve_sha: false
 
     # Whether or not to strip binaries

configs/containers/docker-ubuntu-intel-impi.yaml

@@ -110,8 +110,7 @@ spack:
       os: ubuntu:20.04
       spack:
         url: https://github.com/jcsda/spack
-        # to be replaced by final tag
-        ref: release/1.4.0
+        ref: spack-stack-1.4.0
         resolve_sha: false
 
     # Whether or not to strip binaries

configs/sites/hera/packages.yaml

@@ -57,10 +57,11 @@ packages:
     externals:
     - spec: [email protected]
       prefix: /usr
-  bison:
-    externals:
-    - spec: [email protected]
-      prefix: /usr
+  # Don't use, can lead to duplicate packages
+  #bison:
+  #  externals:
+  #  - spec: [email protected]
+  #    prefix: /usr
   bzip2:
     externals:
     - spec: [email protected]

doc/source/KnownIssues.rst

@@ -11,9 +11,9 @@ General
 
    Our software stack doesn't build with ``gcc@13`` yet. This is also true when combining the LLVM or Apple ``clang`` compiler with ``gfortran@13``.
 
-2. Build errors with Python 3.10
+2. Build errors for ``[email protected]`` with ``[email protected]``
 
-   These build errors have been addressed, it should now be possible to use Python 3.10. Please report errors to the spack-stack developers and, if applicable, to the spack developers.
+   This problem is described in https://github.com/JCSDA/spack-stack/issues/608.
 
 3. Issues starting/finding ``ecflow_server`` due to a mismatch of hostnames
 
@@ -27,6 +27,12 @@ General
 
    We tracked this down to multiple versions of ``bison`` being used. The best solution is to remove external ``bison`` versions earlier than 3.8 from the site config (``packages.yaml``).
 
+==============================
+MSU Hercules
+==============================
+
+1. ``[email protected]`` doesn't build on Hercules, use ``[email protected]`` instead.
+
 ==============================
 NASA Discover
 ==============================
@@ -91,6 +97,12 @@ NAVY HPCMP Narwhal
 
 2. ``[email protected]`` does not build on Narwhal, see https://github.com/JCSDA/spack-stack/issues/524. When using the ``unified-dev`` template, one has to manually remove ``jedi-ufs-env`` and ``ufs-weather-model-env`` from the environment's ``spack.yaml``.
 
+==============================
+NAVY HPCMP Nautilus
+==============================
+
+1. ``[email protected]`` doesn't build on Nautilus, use ``[email protected]`` instead.
+
 ==============================
 macOS
 ==============================