< back to search

gpp_maybe Feature update for spack
SUSE-SLE-Module-HPC-15-SP4-2023-1706

This update for spack fixes the following issues: Version update from 0.17.1 to 0.19.1 (jsc#PED-2803, jsc#PED-3000): - For the full list of features and upstream fixes implemented by this update please consult the release notes at: * https://github.com/spack/spack/releases/tag/v0.19.1 * https://github.com/spack/spack/releases/tag/v0.19.0 * https://github.com/spack/spack/releases/tag/v0.18.1 * https://github.com/spack/spack/releases/tag/v0.18.0 - Bug fixes and improvements: * Make sure the spack environment is set up correctly in spack-generated Dockerfiles (bsc#1207784) * Fix MPI packages not being recognized any more (bsc#1208751) * Fix syntax in post scripts (bsc#1195391) * Fix var_path which that is set incorrectly in version 0.19.0 (bsc#1207053) * Move repositories to `/usr/share/spack`: `/var` is strictly for local data * Improve error message for requirements * Fix libtool filter for Fujitsu compilers * Fix `spack mirror create` to not change paths to urls - Improve `run-find-external.sh` script: * Extend to run `spack compiler find` * Separate triggers for packages and compilers * Better handle when search patterns match multiple directories - Removals and Deprecations: * Support for Python 3.5 is dropped. Only Python 3.6+ are officially supported. * `LD_LIBRARY_PATH` is no longer set by default by spack load or module loads. Setting `LD_LIBRARY_PATH` in Spack environments/modules can cause binaries from outside of Spack to crash, and Spack's own builds use `RPATH` and do not need `LD_LIBRARY_PATH` set in order to run. If you still want the old behavior, you can run these commands to configure Spack to set LD_LIBRARY_PATH: `spack config add modules:prefix_inspections:lib64:[LD_LIBRARY_PATH]` `spack config add modules:prefix_inspections:lib:[LD_LIBRARY_PATH]` * The `spack:concretization:[together|separately]` has been deprecatred. Now use `concretizer:unify:[true|false]` * `config:module_roots` is no longer supported. Use configuration in module sets instead * `spack activate` and `spack deactivate` are no longer supported, having been deprecated in v0.18. Use an environment with a view instead of activating/deactivating (docs) * The old YAML format for buildcaches is now deprecated. If you are using an old buildcache with YAML metadata you will need to regenerate it with JSON metadata. * `spack bootstrap trust` and `spack bootstrap untrust` are deprecated in favor of `spack bootstrap enable` and `spack bootstrap disable` * The `graviton2` architecture has been renamed to `neoverse_n1`, and `graviton3` is now `neoverse_v1`. Buildcaches using the old architecture names will need to be rebuilt * The terms 'blacklist' and 'whitelist' have been replaced with 'include' and 'exclude' in all configuration files. You can use `spack config update` to automatically fix your configuration files

cloud_download Downloads

HPC Module 15.4 x86_64
  • Packages
    spack
    Package manager for HPC systems
    0.19.1-150400.12.5.1 lock rpm lock src
    spack-info
    Info Page for Spack - Package manager for HPC systems
    0.19.1-150400.12.5.3 lock rpm
    spack-man
    Man Page for Spack - Package manager for HPC systems
    0.19.1-150400.12.5.3 lock rpm
    spack-recipes
    Spack built-in package recipes
    0.19.1-150400.12.5.1 lock rpm
HPC Module 15.4 aarch64
  • Packages
    spack
    Package manager for HPC systems
    0.19.1-150400.12.5.1 lock rpm lock src
    spack-info
    Info Page for Spack - Package manager for HPC systems
    0.19.1-150400.12.5.3 lock rpm
    spack-man
    Man Page for Spack - Package manager for HPC systems
    0.19.1-150400.12.5.3 lock rpm
    spack-recipes
    Spack built-in package recipes
    0.19.1-150400.12.5.1 lock rpm