Revisions of spack
buildservice-autocommit
accepted
request 1220059
from
Egbert Eich (eeich)
(revision 110)
baserev update by copy to link target
Egbert Eich (eeich)
accepted
request 1220058
from
Egbert Eich (eeich)
(revision 109)
- Update to version 0.22.2 * Bugfixes - Forward compatibility with Spack 0.23 packages with language dependencies. - Forward compatibility with `urllib` from Python 3.12.6+. - Bump vendored `archspec` for better aarch64 support. - Fix regression in `{variants.X}` and `{variants.X.value}` format strings. - Ensure shell escaping of environment variable values in load and activate commands. - Fix an issue where `spec[pkg]` considers specs outside the current DAG. - Do not halt concretization on unknown variants in externals. - Improve validation of `develop` config section/ - Explicitly disable `ccache` if turned off in config, to avoid cache pollution. - Improve backwards compatibility in `include_concrete`. - Fix issue where package tags were sometimes repeated. - Make `setup-env.sh` "sourced only" by dropping execution bits. - Make certain source/binary fetch errors recoverable instead of a hard error. - Remove debug statements in package hash computation. - Remove redundant clingo warnings. - Remove hard-coded layout version. - Do not initialize previous store state in `use_store`. * Package updates - `chapel` major update/
buildservice-autocommit
accepted
request 1186551
from
Christian Goll (mslacken)
(revision 108)
baserev update by copy to link target
Christian Goll (mslacken)
accepted
request 1186519
from
Egbert Eich (eeich)
(revision 107)
- Update to 0.22.1. * Bug Fixes: - Fix reuse of externals on Linux. - Ensure parent gcc-runtime version >= child. - Ensure the latest gcc-runtime is rpath'ed when multiple exist among link deps. - Improve version detection of glibc. - Improve heuristics for solver. - Make strong preferences override reuse. - Reduce verbosity when C compiler is missing. - Make missing ccache executable an error when required. - Make every environment view containing `python` a `venv`. - Fix external detection for compilers with os but no target. - Fix version optimization for roots. - Handle common implementations of pagination of tags in OCI build caches. - Apply fetched patches to develop specs. - Avoid Windows wrappers for filesystem utilities on non-Windows. - Fix formatting issue in `spack audit`. * Package updates: - Require libiconv for iconv. Notice that glibc/musl also provide iconv, but are not guaranteed to be complete. Set `packages:iconv:require:[glibc]` to restore the old behavior. - protobuf: fix 3.4:3.21 patch checksum. - protobuf: update hash for patch needed when="@3.4:3.21". - git: bump v2.39 to 2.45; deprecate unsafe versions. - gcc: use `-rpath {rpath_dir}` not `-rpath={rpath dir}`. - Remove mesa18 and libosmesa. - Enforce consistency of `gl` providers.
buildservice-autocommit
accepted
request 1179953
from
Egbert Eich (eeich)
(revision 106)
baserev update by copy to link target
Egbert Eich (eeich)
committed
(revision 105)
- Move-site-config-scope-before-system-scope.patch: Give 'site' scope a lower precedence than 'system' scope.
Christian Goll (mslacken)
accepted
request 1174817
from
Egbert Eich (eeich)
(revision 104)
- Give 'site' scope a lower precedence than 'system' scope. The 'site wide' config scope was meant to be per Spack installation. A single system may have multiple Spack installations, so was is meant for overriding the 'system' wide setting per installation. The Spack package is OS-vendor provided. The vendor provides pr generates a configuration which a local admin may want to override. This can now be done from within the 'system' scope. Previously the vendor-supplied configuration was mixed with the 'system' scope - local modifications collided with vendor autoconfiguration. - Add a build-dependency package which will cause build tools and libraries used frequently by Spack to be installed. All these packages are recommended by the main Spack package already. This package may be used in environments where the installation of recommended packages is disabled by default. - Update Spack to version 0.22.0 * New features: - Compiler dependencies: Spack is in the process of making compilers proper dependencies. For this, compiler dependencies are moving from `compilers.yaml` to `packages.yaml` to make this consistent with other externals. For this, dependency graphs will not show the compiler runtime libraries like `gcc-runtime` or `libgfortran`. To minimize disruption, an existing `compilers.yaml` file will continue to work, however, users are encourage to migrate before v0.23. + Packages compiled with `%gcc` now depend on a new package `gcc-runtime`, which contains a copy of the shared compiler
buildservice-autocommit
accepted
request 1168847
from
Christian Goll (mslacken)
(revision 103)
baserev update by copy to link target
Christian Goll (mslacken)
accepted
request 1168824
from
Egbert Eich (eeich)
(revision 102)
- Add lsb-release and zstd as new requires to match upstream prerequisites.
buildservice-autocommit
accepted
request 1164612
from
Christian Goll (mslacken)
(revision 101)
baserev update by copy to link target
Christian Goll (mslacken)
accepted
request 1164574
from
Egbert Eich (eeich)
(revision 100)
- Make `patchelf` a mandatory dependency on products where it is always available.
buildservice-autocommit
accepted
request 1158555
from
Egbert Eich (eeich)
(revision 99)
baserev update by copy to link target
Egbert Eich (eeich)
accepted
request 1158547
from
Egbert Eich (eeich)
(revision 98)
- Add libgfortran, libfl2 and libzip5 to the Spack runtime container as the Spack build container has the corresponding devel packages but these libraries are not installed in a BCI-style base container by default (bsc#1221503).
buildservice-autocommit
accepted
request 1158279
from
Christian Goll (mslacken)
(revision 97)
baserev update by copy to link target
Christian Goll (mslacken)
accepted
request 1158239
from
Egbert Eich (eeich)
(revision 96)
- 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).
buildservice-autocommit
accepted
request 1146129
from
Egbert Eich (eeich)
(revision 95)
baserev update by copy to link target
Egbert Eich (eeich)
accepted
request 1146128
from
Egbert Eich (eeich)
(revision 94)
- Make python version used configurable. - Filter out more rpmlint errors.
buildservice-autocommit
accepted
request 1143572
from
Egbert Eich (eeich)
(revision 93)
baserev update by copy to link target
Egbert Eich (eeich)
committed
(revision 92)
- Minor formatting changes to the changelog.
Egbert Eich (eeich)
accepted
request 1143459
from
Christian Goll (mslacken)
(revision 91)
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
Displaying revisions 1 - 20 of 110