Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2023-08-21 | whizard: new versions 3.1.1 and 3.1.2 (#39540) | Wouter Deconinck | 1 | -0/+2 | |
2023-08-21 | zlib: new version 1.3 (#39539) | Wouter Deconinck | 1 | -0/+1 | |
2023-08-21 | zlib: add git url (#39533) | Wouter Deconinck | 1 | -0/+1 | |
2023-08-18 | cdo: add v2.2.2 (#39506) | Brian Spilner | 1 | -2/+8 | |
* update cdo-2.2.2 * add note on hdf5 | |||||
2023-08-18 | less: update version, dependencies (#39521) | Todd Gamblin | 1 | -0/+3 | |
2023-08-18 | [py-gradio-client] New package (#39496) | Jen Herting | 1 | -0/+27 | |
2023-08-18 | [py-openmim] Beginning work (#39494) | Jen Herting | 1 | -0/+26 | |
2023-08-18 | [py-confection] new package (#39491) | Jen Herting | 1 | -0/+21 | |
2023-08-18 | py-multiqc: add 1.15, correct py-matplotlib dependency (#39509) | George Young | 1 | -1/+2 | |
Co-authored-by: LMS Bioinformatics <bioinformatics@lms.mrc.ac.uk> | |||||
2023-08-18 | py-markdown-it-py: add linkify variant and v2.2.0 (#39492) | Jen Herting | 1 | -0/+6 | |
* [py-markdown-it-py] added linkify variant * [py-markdown-it-py] added version 2.2.0 | |||||
2023-08-18 | fortrilinos: release 2.3.0 compatible with trilinos@14 (#39500) | Seth R. Johnson | 1 | -3/+5 | |
* fortrilinos: release 2.3.0 compatible with trilinos@14.0 | |||||
2023-08-18 | New: py-alpaca-farm, py-alpaca-eval, py-tiktoken; Updated: py-accerlate, ↵ | Benjamin Meyers | 5 | -0/+102 | |
py-transformers (#39432) | |||||
2023-08-18 | WarpX 23.08 (#39407) | Axel Huebl | 3 | -13/+16 | |
* WarpX 23.08 Update WarpX and related Python packages to the lastest releases. * fix style --------- Co-authored-by: eugeneswalker <eugenesunsetwalker@gmail.com> | |||||
2023-08-17 | Updating the versions of available tarballs and adding an eigen3 variant as ↵ | Vijay M | 1 | -14/+22 | |
well (#39498) | |||||
2023-08-17 | `zlib-api`: use `zlib-ng +compat` by default (#39358) | Harmen Stoppels | 1 | -0/+3 | |
In the HPC package manager, we want the fastest `zlib` implementation by default. `zlib-ng` is up to 4x faster than stock `zlib`, and it can do things like take advantage of AVX-512 instructions. This PR makes `zlib-ng` the default `zlib-api` provider (`zlib-api` was introduced earlier, in #37372). As far as I can see, the only issues you can encounter are: 1. Build issues with packages that heavily rely on `zlib` internals. In Gitlab CI only one out of hundreds of packages had that issue (it extended zlib with deflate stuff, and used its own copy of zlib sources). 2. Packages that like to detect `zlib-ng` separately and rely on `zlib-ng` internals. The only issue I've found with this among the hundreds of packages built in CI is `perl` trying to report more specific zlib-ng version details, and relied on some internals that got refactored. But yeah... that warrants a patch / conflict and is nothing special. At runtime, you cannot really have any issues, given that zlib and zlib-ng export the exact same symbols (and zlib-ng tests this in their CI). You can't really have issues with externals when using zlib-ng either. The only type of issue is when system zlib is rather new, and not marked as external; if another external uses new symbols, and Spack builds an older zlib/zlib-ng, then the external might not find the new symbols. But this is a configuration issue, and it's not an issue caused by zlib-ng, as the same would happen with older Spack zlib. * zlib-api: use zlib-ng +compat by default * make a trivial change to zlib-ng to trigger a rebuild * add `haampie` as maintainer | |||||
2023-08-17 | py-flake8: bump including deps (#39426) | Harmen Stoppels | 3 | -0/+8 | |
2023-08-17 | zig: add v0.11.0 (#39484) | Massimiliano Culpo | 1 | -0/+2 | |
2023-08-17 | boost %oneapi: add cxxflags -Wno-error=enum-constexpr-conversion (#39477) | eugeneswalker | 1 | -0/+6 | |
2023-08-17 | gmsh %oneapi: add cflag: -Wno-error=implicit-function-declaration (#39476) | eugeneswalker | 1 | -0/+6 | |
2023-08-17 | py-ruamel-yaml-clib %oneapi: -Wno-error=incompatible-function-pointer-types ↵ | eugeneswalker | 1 | -0/+6 | |
(#39480) | |||||
2023-08-17 | sz %oneapi: add cflag=-Wno-error=implicit-function-declaration (#39467) | eugeneswalker | 1 | -0/+6 | |
2023-08-17 | kokkos: use 'when' instead of 'conflicts' for CUDA variants (#39463) | Seth R. Johnson | 1 | -19/+12 | |
2023-08-17 | silo %oneapi: add cflags: -Wno-error=int, -Wno-error=int-conversion (#39475) | eugeneswalker | 1 | -0/+3 | |
2023-08-17 | py-matplotlib %oneapi: add cxxflags=-Wno-error=register (#39469) | eugeneswalker | 1 | -0/+6 | |
2023-08-17 | py-deepspeed: add new package (#39427) | Adam J. Stewart | 1 | -0/+32 | |
2023-08-17 | snappy: patch and conflict for %nvhpc (#39063) | Sergey Kosukhin | 1 | -0/+15 | |
2023-08-17 | botan: version 3 requires newer GCC (#39450) | Martin Aumüller | 1 | -0/+2 | |
e.g. 3.1.1 produces this during configuration when trying to install: ERROR: This version of Botan requires at least gcc 11.0 | |||||
2023-08-17 | py-setuptools: document Python 3.12 support (#39449) | Adam J. Stewart | 1 | -0/+5 | |
2023-08-17 | py-lightning: add v2.0.7 (#39468) | Adam J. Stewart | 1 | -1/+3 | |
2023-08-16 | py-numcodecs %oneapi: add cflags -Wno-error=implicit-function-declaration ↵ | eugeneswalker | 1 | -0/+6 | |
(#39454) | |||||
2023-08-16 | pruners-ninja cflags: -Wno-error=implicit-function-declaration (#39452) | eugeneswalker | 1 | -0/+6 | |
2023-08-16 | amrex+sycl: restructure constraint on %oneapi (#39451) | eugeneswalker | 1 | -1/+2 | |
2023-08-16 | hdf5-vol-cache %oneapi: cflags: add ↵ | eugeneswalker | 1 | -0/+6 | |
-Wno-error=incompatible-function-pointer-types (#39453) | |||||
2023-08-16 | faodel: update github URL organization to sandialabs (#39446) | Todd Kordenbrock | 1 | -3/+3 | |
2023-08-15 | Fixed HeFFTe package spec to not do the smoke test prior to 2.2.0 (#39435) | Patrick Bridges | 1 | -0/+6 | |
* Fixed HeFFTe package spec to not do the smoke test prior to 2.2.0, where it breaks * Convert test return to 'raise SkipTest' --------- Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com> | |||||
2023-08-15 | Rework conflicts so that "vendors" is not needed anymore | Massimiliano Culpo | 5 | -10/+11 | |
2023-08-15 | Add vendors directive | Massimiliano Culpo | 5 | -9/+28 | |
For the time being this directive prevents the vendored package to be in the same DAG as the one vendoring it. | |||||
2023-08-15 | Improve handling of cases with cycles | Massimiliano Culpo | 2 | -0/+34 | |
To avoid paying the cost of setup and of a full grounding again, move cycle detection into a separate program and check first if the solution has cycles. If it has, ground only the integrity constraint preventing cycles and solve again. | |||||
2023-08-15 | Fix ecp-data-vis-sdk: a package cannot impose constraints on transitive deps | Massimiliano Culpo | 1 | -1/+1 | |
2023-08-15 | Add unit-tests for use cases requiring separate concretization of build deps | Massimiliano Culpo | 8 | -0/+129 | |
2023-08-15 | Construct unification sets on demand, improve heuristic | Massimiliano Culpo | 1 | -0/+2 | |
2023-08-15 | adding new rpp package (#38942) | afzpatel | 4 | -0/+189 | |
* initial commit for adding new rpp package * fix styling | |||||
2023-08-15 | Add mold 2.1.0 (#39443) | Mikael Simberg | 1 | -0/+1 | |
2023-08-15 | Add version HDF5 1.14.2 (#39409) | Larry Knox | 1 | -0/+5 | |
* Add version HDF5 1.14.2 | |||||
2023-08-15 | arborx: new version and patch for 1.4 with Trilinos (#39438) | Andrey Prokopenko | 2 | -0/+18 | |
* arborx: patch 1.4 for Trilinos 14.0 * arborx: version 1.4.1 | |||||
2023-08-15 | Add gperftools 2.11 (#39440) | Mikael Simberg | 1 | -0/+1 | |
2023-08-15 | squashfs: Add static variant (#39433) | Bryan Herman | 1 | -0/+7 | |
2023-08-14 | intel-xed: add version 2023.07.09 (#39436) | Mark W. Krentel | 1 | -0/+1 | |
2023-08-14 | Spiner and ports-of-call updates (#39437) | Richard Berger | 2 | -0/+2 | |
* ports-of-call: new version 1.5.2 * spiner: new version 1.6.2 | |||||
2023-08-14 | Windows: executable/path handling (#37762) | markus-ferrell | 2 | -7/+7 | |
Windows executable paths can have spaces in them, which was leading to errors when constructing Executable objects: the parser was intended to handle cases where users could provide an executable along with one or more space-delimited arguments. * Executable now assumes that it is constructed with a string argument that represents the path to the executable, but no additional arguments. * Invocations of Executable.__init__ that depended on this have been updated (this includes the core, tests, and one instance of builtin repository package). * The error handling for failed invocations of Executable.__call__ now includes a check for whether the executable name/path contains a space, to help users debug cases where they (now incorrectly) concatenate the path and the arguments. |