baserev update by copy to link target

• Files Changed
• Browse Source

moved lua_lmod to Recommends

• Files Changed
• Browse Source

        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

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

with gcc13

• Files Changed
• Browse Source

- 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

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

fix doc build

• Files Changed
• Browse Source

- 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:

• Files Changed
• Browse Source

- removed Add-zypper-to-the-valid-container.os_packages-commands.patch 
  as incoperated upstream

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- 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)

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

fixed more env stuff

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

rempved powershell stuff and some relevant shebangs

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

  * Spack hashes now include link, run, and build dependencies, as well as a
    canonical hash of package recipes. Previously, hashes only included link
    and run dependencies (though build dependencies were stored by
    environments). We coarsened the hash to reduce churn in user installations,
    but the new default concretizer behavior mitigates this concern and gets us
    reuse and provenance.  You will be able to see the build dependencies of
    new installations
  * concretizer:unify:when_possible will try to resolve a fully unified
    environment, but if it cannot, it will create multiple configurations of
    some packages where it has to.  with spack find.
  * Spack now has an updated binary format, with improvements for security. The
    new format has a detached signature file, and Spack verifies the signature
    before untarring or decompressing the binary package. The previous format
    embedded the signature in a tar file, which required the client to run tar
    before verifying (#30750). Spack can still install from build caches using
    the old format, but we encourage users to switch to the new format going
    forward.
  * The spack bootstrap mirror command can automatically create a mirror for
    bootstrapping the concretizer and other needed dependencies in an
    air-gapped environment.
  * spack env depfile can be used to generate a Makefile from an environment,
    which can be used to build packages the environment in parallel on a single
    node
  * In addition to being conditional themselves, variants can now have
    conditional values that are only possible for certain configurations of a
    package.

• Files Changed
• Browse Source

  * 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

• Files Changed
• Browse Source

- 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

• Files Changed
• Browse Source