Age | Commit message (Collapse) | Author | Files | Lines |
|
weaviate: 1.24.4 -> 1.24.6
|
|
|
|
|
|
|
|
|
|
weaviate: 1.24.1 -> 1.24.4
|
|
Conflicts:
- pkgs/development/python-modules/flask-security-too/default.nix
|
|
Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
|
|
Conflicts:
- pkgs/development/python-modules/sphinx-autobuild/default.nix
|
|
treewide: add meta.mainProgram to (almost) all packages with a single binary
|
|
The nixpkgs-unstable channel's programs.sqlite was used to identify
packages producing exactly one binary, and these automatically added
to their package definitions wherever possible.
|
|
|
|
|
|
into libcxx (#292043)
- merge libcxxabi into libcxx for LLVM 12, 13, 14, 15, 16, 17, and git.
- remove the link time workaround `-lc++ -lc++abi` from 58 packages as it is no longer required.
- fixes https://github.com/NixOS/nixpkgs/issues/166205
- provides alternative fixes for. https://github.com/NixOS/nixpkgs/issues/269548 https://github.com/NixOS/nix/issues/9640
- pkgsCross.x86_64-freebsd builds work again
This change can be represented in 3 stages
1. merge libcxxabi into libcxx -- files: pkgs/development/compilers/llvm/[12, git]/{libcxx, libcxxabi}
2. update stdenv to account for merge -- files: stdenv.{adapters, cc.wrapper, darwin}
3. remove all references to libcxxabi outside of llvm (about 58 packages modified)
### merging libcxxabi into libcxx
- take the union of the libcxxabi and libcxx cmake flags
- eliminate the libcxx-headers-only package - it was only needed to break libcxx <-> libcxxabi circular dependency
- libcxx.cxxabi is removed. external cxxabi (freebsd) will symlink headers / libs into libcxx.
- darwin will re-export the libcxxabi symbols into libcxx so linking `-lc++` is sufficient.
- linux/freebsd `libc++.so` is a linker script `LINK(libc++.so.1, -lc++abi)` making `-lc++` sufficient.
- libcxx/default.nix [12, 17] are identical except for patches and `LIBCXX_ADDITIONAL_LIBRARIES` (only used in 16+)
- git/libcxx/defaul.nix does not link with -nostdlib when useLLVM is true so flag is removed. this is not much different than before as libcxxabi used -nostdlib where libcxx did not, so libc was linked in anyway.
### stdenv changes
- darwin bootstrap, remove references to libcxxabi and cxxabi
- cc-wrapper: remove c++ link workaround when libcxx.cxxabi doesn't exist (still exists for LLVM pre 12)
- adapter: update overrideLibcxx to account for a pkgs.stdenv that only has libcxx
### 58 package updates
- remove `NIX_LDFLAGS = "-l${stdenv.cc.libcxx.cxxabi.libName}` as no longer needed
- swift, nodejs_v8 remove libcxxabi references in the clang override
https://github.com/NixOS/nixpkgs/pull/292043
|
|
|
|
|
|
|
|
meilisearch: 1.6.1 -> 1.6.2
|
|
|
|
|
|
Diff: https://github.com/valeriansaliou/sonic/compare/refs/tags/v1.4.3...v1.4.8
Changelog: https://github.com/valeriansaliou/sonic/releases/tag/v1.4.8
|
|
|
|
weaviate: 1.23.1 -> 1.23.7
|
|
meilisearch: 1.6.0 -> 1.6.1
|
|
|
|
|
|
|
|
elasticsearch: 7.17.10 -> 7.17.16
|
|
|
|
|
|
|
|
Fixes CVE-2023-31417, CVE-2023-31418, CVE-2023-31419, CVE-2023-46673 and CVE-2023-46674.
Security announces:
https://www.elastic.co/guide/en/security/7.17/release-notes-header-7.17.0.html#release-notes-7.17.16
Release notes:
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.16.html
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.15.html
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.14.html
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.13.html
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.12.html
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/release-notes-7.17.11.html
|
|
|
|
|
|
|
|
|
|
Conflicts:
- pkgs/development/python-modules/sabctools/default.nix
|
|
|
|
|
|
qdrant: 1.6.1 -> 1.7.3
|
|
|
|
groonga: 13.0.9 -> 13.1.0
|
|
|
|
|
|
weaviate: 1.21.7 -> 1.23.0
|
|
|
|
|
|
|
|
|
|
The setuptools-scm packages gained a setup hook, that sets it to the
derivation version automatically, so setting it to that manually has
become redundant.
This also affects downstream consumers of setuptools-scm, like hatch-vcs
or flit-scm.
|