- Update Spack to version 0.21.2
* Bugfixes
+ Containerize: accommodate nested or pre-existing `spack-env`
paths.
+ Fix `setup-env` script, when going back and forth between
instances.
+ Fix using fully-qualified namespaces from root specs.
+ Fix a bug when a required provider is requested for multiple
virtuals.
+ OCI buildcaches:
* only push in parallel when forking.
* use pickleable errors (#42160)
+ Fix using sticky variants in externals.
+ Fix a rare issue with conditional requirements and
multi-valued variants.
* Package updates
+ `rust`: add v1.75, rework a few variants.
+ `py-transformers`: add v4.35.2.
- Fix path to setup-env.sh in the Apptainer template (bsc#1221471).
OBS-URL: https://build.opensuse.org/request/show/1158239
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=96
fix infinite recursion when computing concretization
errors
+ environment: fix an issue with
deconcretization/reconcretization of specs
+ buildcache: don't error if a patch is missing, when
installing from binaries
In v0.18, we added better error messages that could tell you
what problem happened, but they couldn't tell you why it
happened. 0.21 adds condition chaining to the solver, and
Spack can now trace back through the conditions that led to
an error and build a tree of causes potential causes and
where they came from.
This creates a container image from the Spack installations
on the host system, without the need to run spack install
from a Dockerfile or sif file. It also addresses the
inconvenience of losing binaries of dependencies when RUN
spack install fails inside docker build. Further, the
container image layers and build cache tarballs are the same
files. This means that spack install and docker pull use the
exact same underlying binaries. If you previously used spack
install inside of docker build, this feature helps you save
storage by a factor two.
Increasingly, complex package builds require multiple
versions of some build dependencies. For example, Python
packages frequently require very specific versions of
setuptools, cython, and sometimes different physics packages
require different versions of Python to build. The
concretizer enforced that every solve was unified, i.e.,
that there only be one version of every package. The
concretizer now supports "duplicate" nodes for build
OBS-URL: https://build.opensuse.org/request/show/1143459
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=91
- update to 0.21.1
* Add support for reading buildcaches created by Spack v0.22
* Bugfixes
+ spack graph: fix coloring with environments
+ spack info: sort variants in --variants-by-name
+ Spec.format: error on old style format strings
+ ASP-based solver:
fix infinite recursion when computing concretization errors
don't error for type mismatch on preferences
don't emit spurious debug output
+ Improve the error message for deprecated preferences
+ Fix MSVC preview version breaking clingo build on Windows
+ Fix multi-word aliases
+ Add a warning for unconfigured compiler
+ environment: fix an issue with deconcretization/reconcretization of specs
+ buildcache: don't error if a patch is missing, when installing from binaries
- updated to 0.21.0
* following new features:
+ Better error messages with condition chaining:
In v0.18, we added better error messages that could tell you what problem
happened, but they couldn't tell you why it happened. 0.21 adds condition
chaining to the solver, and Spack can now trace back through the conditions
that led to an error and build a tree of causes potential causes and where
they came from.
+ OCI build caches:
You can now use an arbitrary OCI registry as a build cache:
```
$ spack mirror add my_registry oci://user/image # Dockerhub
$ spack mirror add my_registry oci://ghcr.io/haampie/spack-test # GHCR
$ spack mirror set --push --oci-username ... --oci-password ... my_registry # set login creds
OBS-URL: https://build.opensuse.org/request/show/1141708
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=90
connection info.
+ Fix a minor issue with package hash computation for Python 3.12.
+ Improve escaping in Tcl module files.
+ Make repo cache work on repositories with zero mtime.
+ Ignore errors for newer, incompatible buildcache version.
+ Print an error when git is required, but missing.
+ Ensure missing build dependencies get installed when using
`spack install --overwrite`.
+ Fix an issue where Spack freezes when the build process
unexpectedly exits.
+ Fix a bug where installation failures cause an unrelated
`NameError` to be thrown.
+ Fix an issue where Spack package versions would be incorrectly
derived from git tags.
+ Fix a bug triggered when file locking fails internally.
+ Prevent `spack external find` to error out when a directory
cannot be accessed.
+ Fix multiple performance regressions in environments.
+ Add more ignored modules to `pyproject.toml` for mypy.
+ Spack now supports Python 3.12.
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=87
Update to version 0.20.3 with the following changes:
* Bug fixes:
+ Fix a bug where spack mirror set-url would drop configured connection info
+ Fix a minor issue with package hash computation for Python 3.12
+ Improve escaping in Tcl module files
+ Make repo cache work on repositories with zero mtime
+ Ignore errors for newer, incompatible buildcache version
+ Print an error when git is required, but missing
+ Ensure missing build dependencies get installed when using spack install --overwrite
+ Fix an issue where Spack freezes when the build process unexpectedly exits
+ Fix a bug where installation failures cause an unrelated NameError to be thrown
+ Fix an issue where Spack package versions would be incorrectly derived from git tags
+ Fix a bug triggered when file locking fails internally
+ Prevent "spack external find" to error out when a directory cannot be accessed
+ Fix multiple performance regressions in environments
+ Add more ignored modules to pyproject.toml for mypy
* Features:
+ Spack now supports Python 3.12
rebased Fix-error-during-documentation-build-due-to-recursive-module-inclusion.patch
OBS-URL: https://build.opensuse.org/request/show/1123507
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=86
- Update to version 0.20.1 with the following changes:
* Bug fixes:
+ Fix spec removed from an environment where not actually
removed if `--force` was not given.
+ Hotfix for a few recipes that treat CMake as a link
dependency.
+ Fix re-running stand-alone test a second time, which was
getting a trailing spurious failure.
+ Fix reading JSON manifest on Cray, reporting non-concrete
specs.
+ Fix a few bugs when generating Dockerfiles from Spack.
+ Fix a few long-standing bugs when generating module files.
+ Fix issues with building Python extensions when using an
external Python.
+ Fix `spack compiler remove`: remove from command line even
if they appear in different scopes.
* Features:
+ Speed-up module file generation.
+ Show external status as `[e]`.
+ Backport `archspec` fixes.
+ Improve a few error messages.
OBS-URL: https://build.opensuse.org/request/show/1110679
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=84
- Update to version 0.20.0 with the following features:
* Exact versions: Spack did not previously have a way to distinguish a
version if it was a prefix of some other version. For example, @3.2 would
match 3.2, 3.2.1, 3.2.2, etc. You can now match exactly 3.2 with @=3.2.
This is useful, for example, if you need to patch only the 3.2 version of a
package
* More stable concretization: Now, spack concretize will only concretize the
new portions of the environment and will not change existing parts of an
environment unless you specify --force. This has always been true for
unify:false, but not for unify:true and unify:when_possible environments.
* The concretizer has a new --reuse-deps argument that only reuses dependencies.
That is, it will always treat the roots of your environment as it would with
--fresh. This allows you to upgrade just the roots of your environment while
keeping everything else stable
* Specs in buildcaches can be referenced by hash: Previously, you could run
spack buildcache list and see the hashes in buildcaches, but referring to
them by hash would fail. You can now run commands like spack spec and
spack install and refer to buildcache hashes directly, e.g. spack install
/abc123
* New package and buildcache index websites
Our public websites for searching packages have been completely revamped
and updated. You can check them out here:
Package Index: https://packages.spack.io
Buildcache Index: https://cache.spack.io
Both are searchable and more interactive than before. Currently major
releases are shown; UI for browsing develop snapshots is coming soon.
* Default CMake and Meson build types are now Release: Spack has historically
defaulted to building with optimization and debugging, but packages like
llvm can be enormous with debug turned on. Our default build type for all
Spack packages is now Release. This has a number of benefits:
OBS-URL: https://build.opensuse.org/request/show/1088985
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=72
- Udpate to 0.19.1 with following bug fixes:
* buildcache create: make "file exists" less verbose
* spack mirror create: don't change paths to urls
* Improve error message for requirements
* Fix libtool filter for Fujitsu compilers
* FileCache: delete the new cache file on exception
- using `--all` flag for `spack external find` in the %triggrin
section, as MPI packages were not recognized any more, fixing
(bsc#1208751)
OBS-URL: https://build.opensuse.org/request/show/1068458
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=61
- updated to version 0.19.0 with follwoinig changes:
* Spack's traditional package preferences are soft, but we've added hard
requriements to packages.yaml and spack.yaml
* spack install in an environment will no longer add to the specs: list; you'll
need to either use spack add <spec> or spack install --add <spec>.
* spack uninstall will not remove from your environment's specs:
list; you'll need to use spack remove or spack uninstall --remove.
* concretizer:unify:true is now the default mode for new environments
* include environment configuration from URLs
* An increasing number of packages in the ecosystem need the ability to
support multiple build systems
* package ++variant:
enabled variant that will be propagated to dependencies
* git. prefix to specify git tags or branches as versions. All of these are
valid git versions in
* spack ci generate --tests will generate a .gitlab-ci.yml file that not only
does builds but also runs tests for built packages
* spack test run --explicit will only run tests for packages that are
explicitly installed, instead of all packages.
* You can add a new shared_linking option to config.yaml to make Spack embed absolute paths
to needed shared libraries in ELF executables and shared libraries on Linux
* spack spec prints dependencies more legibly. Dependencies in the output now
appear at the earliest level of indentation possible (#33406)
* You can override package.py attributes like url, directly in packages.yaml
* There are a number of new architecture-related format strings you can use
in Spack configuration files to specify paths
- Improvement from v0.18.0
* spack install --reuse was introduced in v0.17.0, and --reuse is now the
default concretization mode. Spack will try hard to resolve dependencies
using installed packages or binaries
OBS-URL: https://build.opensuse.org/request/show/1037625
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=49
- Fix: Fix-error-during-documentation-build-due-to-recursive-module-inclusion.patch
This is needed to prevent an AttributeError during
'import spack.environment as some_name'
when building Sphinx documentation - due to an outdated
Python on SLE.
The original version caused errors:
'NameError: name 'uenv' is not defined'
when using 'spack env activate' et.al. (bsc#1198212).
OBS-URL: https://build.opensuse.org/request/show/967985
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=45
- updated to version 0.17.0
(Upstream feature/bug references (<ID>) are relative to
https://github.com/spack/spack/issues/<ID>).
* New concretizer is now default
The new concretizer introduced as an experimental feature in v0.16.0
is now the default (#25502). The new concretizer is based on the
clingo logic programming system,
and it enables us to do much higher quality and faster dependency solving
The old concretizer is still available via the concretizer: original
setting, but it is deprecated and will be removed in v0.18.0.
* Binary Bootstrapping
To make it easier to use the new concretizer and binary packages,
Spack now bootstraps clingo and GnuPG from public binaries. If it
is not able to bootstrap them from binaries, it installs them from
source code. With these changes, you should still be able to clone Spack
and start using it almost immediately.
* Reuse existing packages (experimental)
The most wanted feature from our
2020 user survey and
the most wanted Spack feature of all time (#25310). spack install,
spack spec, and spack concretize now have a --reuse option, which
causes Spack to minimize the number of rebuilds it does. The --reuse
option will try to find existing installations and binary packages locally
and in registered mirrors, and will prefer to use them over building new
versions. This will allow users to build from source far less than in
prior versions of Spack. This feature will continue to be improved, with
configuration options and better CLI expected in v0.17.1. It will become
the default concretization mode in v0.18.0.
* Better error messages
We have improved the error messages generated by the new concretizer by
OBS-URL: https://build.opensuse.org/request/show/931785
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=35
