df5bf03d36
- Update to version 0.23.1
* Fix a correctness issue of `ArchSpec.intersects`.
* Make extra_attributes order independent in Spec hashing.
* Fix issue where system proxy settings were not respected in OCI
build caches.
* Fix an issue where the `--test` concretizer flag was not
forwarded correctly.
* Fix an issue where `codesign` and `install_name_tool` would
not preserve hardlinks on Darwin.
* Fix an issue on Darwin where codesign would run on unmodified
binaries.
* Patch configure scripts generated with libtool < 2.5.4, to
avoid redundant flags when creating shared libraries on Darwin.
* Ensure proper UTF-8 encoding/decoding in logging.
* Fix issues related `to filter_file`.
* Fix an issue related to creating bootstrap source mirrors.
* Fix an issue where command line config arguments were not
always top level.
* Fix an incorrect typehint of `concretized()`.
* Improve mention of next Spack version in warning.
Tests: fix forward compatibility with Python 3.13.
* Docs: encourage use of `--oci-username-variable` and
`--oci-password-variable`.
* Docs: ensure Getting Started has bootstrap list output in
correct place. (forwarded request 1247374 from eeich)
OBS-URL: https://build.opensuse.org/request/show/1247375
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/spack?expand=0&rev=49
openSUSE/SUSE specific Settings ============================================= The packages build by a regular user are stored in the home directory and so only available for this user. When the packages should be available for all users on a system, the user who builds the packages, must be able to write to the global spack user directories under /usr/lib/spack/ Packages stored under this path are available for all user via lmod. To add a user to the group spack so that he can write to the global spack directory, execute (as root): # usermod -a -G spack <user_login> and change the setting for 'install_tree:' to the global spack directory in the configuration '~/.spack/config.yaml' for this user. NOTE: As the recipes are contributed by the spack community and rely also on external packages, a signification part of the recipes may fail to create packages.