with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper
this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists
in env cause a eval failure
...but still allow for setting `dataDir` to a custom path. This gets
rid of the use of the deprecated option PermissionsStartOnly. Also, add
the ability to customize user and group, since that could be useful
with a custom `dataDir`.
Done with the help of https://github.com/Mindavi/nixpkgs-mark-broken
Tool is still WIP but this is one of the first results.
I manually audited the results and removed some results that were not valid.
Note that some of these packages maybe should have more constrained platforms set
instead of broken set, but I think not being perfectly correct is better than
just keep trying to build all these things and never succeeding.
Some observations:
- Some darwin builds require XCode tools
- aarch64-linux builds sometimes suffer from using gcc9
- gcc9 is getting older and misses some new libraries/features
- Sometimes tools try to do system detection or expect some explicit settings for
platforms that are not x86_64-linux
glibc's libcrypt is deprecated and since
ff30c899d8
is built by default without libcrypt, that's probably the point when `elasticsearch6`
started failing with
```
auto-patchelf: 3 dependencies could not be satisfied
error: auto-patchelf could not satisfy dependency libcrypt.so.1 wanted by /nix/store/nd0gn95yfnnmnnw8zk2jnafc9gj2qy91-elasticsearch-6.8.21/modules/x-pack-ml/platform/linux-x86_64/lib/liblog4cxx.so.10
error: auto-patchelf could not satisfy dependency libcrypt.so.1 wanted by /nix/store/nd0gn95yfnnmnnw8zk2jnafc9gj2qy91-elasticsearch-6.8.21/modules/x-pack-ml/platform/linux-x86_64/lib/libaprutil-1.so.0
error: auto-patchelf could not satisfy dependency libcrypt.so.1 wanted by /nix/store/nd0gn95yfnnmnnw8zk2jnafc9gj2qy91-elasticsearch-6.8.21/modules/x-pack-ml/platform/linux-x86_64/lib/libapr-1.so.0
```
Let's add libxcrypt dependency, also note that `elasticsearch6-oss` doesn't
seem to need it.
Should resolve https://github.com/NixOS/nixpkgs/issues/203467
Extra note is elk6 may get removed from nixpkgs soon in favor of elk7
https://github.com/NixOS/nixpkgs/pull/194420
The solr update in #161875 has gone nowhere sofar, while multiple CVEs
are lingering, which makes this a prime candidate to mark insecure.
The maintainer has indicated they wanted to remove themself, which has
not happened yet, so this takes care of that.
https://github.com/NixOS/nixpkgs/pull/161875#issuecomment-1058025102
* elk7: 7.11.1 -> 7.16.1
* nixosTests.elk: Improve reliability and compatibility with ELK 7.x
- Use comparisons in jq instead of grepping
- Match for `.hits.total.value` if version >= 7, otherwise it always
passes
- Make curl fail if requests fails
* nixos/filebeat: Add initial module and test
Filebeat is an open source file harvester, mostly used to fetch logs
files and feed them into logstash.
This module can be used instead of journalbeat if used with
`filebeat7` and configured with the `journald` input.
* python3Packages.parsedmarc.tests: Fix breakage
- Don't use the deprecated elasticsearch7-oss package
- Improve jq query robustness and add tracing
* rl-2205: Note the addition of the filebeat service
* elk6: 6.8.3 -> 6.8.21
The latest version includes a fix for CVE-2021-44228.
* nixos/journalbeat: Add a loose dependency on elasticsearch
Avoid unnecssary back-off when elasticsearch is running on the same
host.
Fixes dependency error while building search-guard:
Exception in thread "main" java.lang.IllegalArgumentException: Missing plugin [lang-painless], dependency of [search-guard-7]
The options as specified were not a coherent set. There were three
things to consider: autoPatchelfHook, the regular rpath
fixup (controlled by dontPatchELF) and the elf interpreter rewrite in
the postFixup hook.
The autoPatchelfHook will set the interpreter, so the explicit
invocation of patchelf to do so in postFixup should not be required.
The autoPatchelfHook will rewrite rpaths entirely, so disabling the
rpath minimizing via dontPatchELF should have no effect.
Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in
which cargo vendor erroneously changed permissions of vendored
crates. This was fixed in Rust
1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all
cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are
potentially broken.
This change updates cargoSha256/cargoHash tree-wide.
Fixes#121994.
continuation of #109595
pkgconfig was aliased in 2018, however, it remained in
all-packages.nix due to its wide usage. This cleans
up the remaining references to pkgs.pkgsconfig and
moves the entry to aliases.nix.
python3Packages.pkgconfig remained unchanged because
it's the canonical name of the upstream package
on pypi.
According to https://repology.org/repository/nix_unstable/problems, we have a
lot of packages that have http links that redirect to https as their homepage.
This commit updates all these packages to use the https links as their
homepage.
The following script was used to make these updates:
```
curl https://repology.org/api/v1/repository/nix_unstable/problems \
| jq '.[] | .problem' -r \
| rg 'Homepage link "(.+)" is a permanent redirect to "(.+)" and should be updated' --replace 's@$1@$2@' \
| sort | uniq > script.sed
find -name '*.nix' | xargs -P4 -- sed -f script.sed -i
```
There ver very many conflicts, basically all due to
name -> pname+version. Fortunately, almost everything was auto-resolved
by kdiff3, and for now I just fixed up a couple evaluation problems,
as verified by the tarball job. There might be some fallback to these
conflicts, but I believe it should be minimal.
Hydra nixpkgs: ?compare=1538299
This adds the following new packages:
+ elasticsearch7
+ elasticsearch7-oss
+ logstash7
+ logstash7-oss
+ kibana7
+ kibana7-oss
+ filebeat7
+ heartbeat7
+ metricbeat7
+ packetbeat7
+ journalbeat7
The default major version of the ELK stack stays at 6. We should
probably set it to 7 in a next commit.
The unfree variant of elasticsearch uses autoPatchelfHook and since we
removed the dependency on file for the hook itself in
58a97dfb49 we no longer have zlib
propagated.
So we need to explicitly state that dependency here.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @apeschar, @basvandijk
* The ELK stack is upgraded to 6.3.2.
* `elasticsearch6`, `logstash6` and `kibana6` now come with X-Pack which is
a suite of additional features. These are however licensed under the unfree
"Elastic License".
* Fortunately they also provide OSS versions which are now packaged
under: `elasticsearch6-oss`, `logstash6-oss` and `kibana6-oss`.
Note that the naming of the attributes is consistent with upstream.
* The test `nix-build nixos/tests/elk.nix -A ELK-6` will test the OSS
version by default. You can also run the test on the unfree ELK using:
`NIXPKGS_ALLOW_UNFREE=1 nix-build nixos/tests/elk.nix -A ELK-6 --arg enableUnfree true`
* treewide: http -> https sources
This updates the source urls of all top-level packages from http to
https where possible.
* buildtorrent: fix url and tab -> spaces
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/groonga/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/av4a5br78r73h7r6mlbqg3zxi9lksskq-groonga-8.0.2/bin/groonga-suggest-create-dataset -h’ got 0 exit code
- ran ‘/nix/store/av4a5br78r73h7r6mlbqg3zxi9lksskq-groonga-8.0.2/bin/groonga-suggest-create-dataset --help’ got 0 exit code
- ran ‘/nix/store/av4a5br78r73h7r6mlbqg3zxi9lksskq-groonga-8.0.2/bin/groonga -h’ got 0 exit code
- ran ‘/nix/store/av4a5br78r73h7r6mlbqg3zxi9lksskq-groonga-8.0.2/bin/groonga --help’ got 0 exit code
- ran ‘/nix/store/av4a5br78r73h7r6mlbqg3zxi9lksskq-groonga-8.0.2/bin/groonga-httpd -h’ got 0 exit code
- found 8.0.2 with grep in /nix/store/av4a5br78r73h7r6mlbqg3zxi9lksskq-groonga-8.0.2
- directory tree listing: https://gist.github.com/9a3a3eb436d26334ce117be25e74b45c
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/groonga/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/q7ml0yi4cgbk80hzsps8ili5c6iypp4r-groonga-8.0.1/bin/groonga-suggest-create-dataset -h’ got 0 exit code
- ran ‘/nix/store/q7ml0yi4cgbk80hzsps8ili5c6iypp4r-groonga-8.0.1/bin/groonga-suggest-create-dataset --help’ got 0 exit code
- ran ‘/nix/store/q7ml0yi4cgbk80hzsps8ili5c6iypp4r-groonga-8.0.1/bin/groonga -h’ got 0 exit code
- ran ‘/nix/store/q7ml0yi4cgbk80hzsps8ili5c6iypp4r-groonga-8.0.1/bin/groonga --help’ got 0 exit code
- ran ‘/nix/store/q7ml0yi4cgbk80hzsps8ili5c6iypp4r-groonga-8.0.1/bin/groonga-httpd -h’ got 0 exit code
- found 8.0.1 with grep in /nix/store/q7ml0yi4cgbk80hzsps8ili5c6iypp4r-groonga-8.0.1
- directory tree listing: https://gist.github.com/082e5c57cc92d0367e65c277e2f6dd90
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/rd3zgq55rdmmyd4rfbv2ij98bk55icic-sphinxsearch-2.2.11/bin/sphinxsearch-searchd -h` got 0 exit code
- ran `/nix/store/rd3zgq55rdmmyd4rfbv2ij98bk55icic-sphinxsearch-2.2.11/bin/sphinxsearch-searchd --help` got 0 exit code
- ran `/nix/store/rd3zgq55rdmmyd4rfbv2ij98bk55icic-sphinxsearch-2.2.11/bin/sphinxsearch-searchd -h` and found version 2.2.11
- ran `/nix/store/rd3zgq55rdmmyd4rfbv2ij98bk55icic-sphinxsearch-2.2.11/bin/sphinxsearch-searchd --help` and found version 2.2.11
- found 2.2.11 with grep in /nix/store/rd3zgq55rdmmyd4rfbv2ij98bk55icic-sphinxsearch-2.2.11
- found 2.2.11 in filename of file in /nix/store/rd3zgq55rdmmyd4rfbv2ij98bk55icic-sphinxsearch-2.2.11
cc "@ederoyd46"
* pkgs: refactor needless quoting of homepage meta attribute
A lot of packages are needlessly quoting the homepage meta attribute
(about 1400, 22%), this commit refactors all of those instances.
* pkgs: Fixing some links that were wrongfully unquoted in the previous
commit
* Fixed some instances
* Add kibana5 and logstash5
* Upgrade the elastic beats to 5.4
* Make sure all elastic products use the same version
(see elk5Version)
* Add a test for the ELK stack
