Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/di/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/8vbvsrd7iwc19w4p86ydkmr9bxb2nnpj-di-4.46/bin/mi -h’ got 0 exit code
- ran ‘/nix/store/8vbvsrd7iwc19w4p86ydkmr9bxb2nnpj-di-4.46/bin/mi --help’ got 0 exit code
- ran ‘/nix/store/8vbvsrd7iwc19w4p86ydkmr9bxb2nnpj-di-4.46/bin/di -h’ got 0 exit code
- ran ‘/nix/store/8vbvsrd7iwc19w4p86ydkmr9bxb2nnpj-di-4.46/bin/di --help’ got 0 exit code
- found 4.46 with grep in /nix/store/8vbvsrd7iwc19w4p86ydkmr9bxb2nnpj-di-4.46
- directory tree listing: https://gist.github.com/d35cd075cfb508460c77f21a1cae002e
As suggested in https://github.com/NixOS/nixpkgs/pull/39416#discussion_r183845745
the versioning attributes in `lib` should be consistent to
`nixos/version` which implicates the following changes:
* `lib.trivial.version` -> `lib.trivial.release`
* `lib.trivial.suffix` -> `lib.trivial.versionSuffix`
* `lib.nixpkgsVersion` -> `lib.version`
As `lib.nixpkgsVersion` is referenced several times in `NixOS/nixpkgs`,
`NixOS/nix` and probably several user's setups. As the rename will cause
a notable impact it's better to keep `lib.nixpkgsVersion` as alias with
a warning yielded by `builtins.trace`.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/hwinfo/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/hwinfo -h’ got 0 exit code
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/hwinfo --help’ got 0 exit code
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/hwinfo --version’ and found version 21.53
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/check_hd help’ got 0 exit code
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/getsysinfo -h’ got 0 exit code
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/getsysinfo --help’ got 0 exit code
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/getsysinfo help’ got 0 exit code
- found 21.53 with grep in /nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53
- directory tree listing: https://gist.github.com/c3f6d76aa5a198a4ded2f2598380a0ef
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
The package was originally broken as reported in #38940 and
facebook/osquery#4257. The latest version (3.x) contains several
important fixes for GCC 7, so now we can compile without a much less
complicated patches.
The following changes were needed to fix the derivation:
* Upgrade `osquery/third-party` to the latest rev to be compliant with
osquery 3.
* Keep using an override for the AWS SDK (for a lower closure size and
less compile time), but make the `ec2` API available.
* Added the dependencies `fpm`, `zstd`, `rdkafka`, `rapidjson` to the
build. `linenoise-ng` is obsolete as it's directly bundled with
`osquery/third-party`.
* Fixed the linking issue with `gflags` as recommended in the mailing
list: https://groups.google.com/d/msg/nix-devel/l1blj-mWxtI/J3CwPATBCAAJ
* Dropped the obsolete dependencies `cpp-netlib`, `lz4`, `apt` and
`devicemapper` (thanks @Infinisil).
* Override `OSQUERY_PLATFORM` to provide `nixos:version`
for sandbox and non-NixOS based builds. The `platform-nixos.patch`
file is now obsolete (thanks @flokli).
The patch was rebased against the 3.x branch of `osquery` and contains
mostly old changes. Additionally several testing targets were skipped as
they broke the build.
The functionality has been testing using the following command:
```
mkdir /tmp/osq.log/
./result/bin/osqueryd --pidfile /tmp/osq.pid \
--database_path /tmp/test.db --logger_path /tmp/osq.log
```
With the daemon running the database can be queried easily using
`./result/bin/osqueryi`.
Fixes ticket #38940
See ticket #36453
Further reference can be gathered from the affected Hydra logs for
the master branch: https://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.osquery.x86_64-linux
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/facter/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/p374zrqr6q2q61jfkfmh1i56wrszhln4-facter-3.11.1/bin/facter -h’ got 0 exit code
- ran ‘/nix/store/p374zrqr6q2q61jfkfmh1i56wrszhln4-facter-3.11.1/bin/facter --help’ got 0 exit code
- ran ‘/nix/store/p374zrqr6q2q61jfkfmh1i56wrszhln4-facter-3.11.1/bin/facter help’ got 0 exit code
- found 3.11.1 with grep in /nix/store/p374zrqr6q2q61jfkfmh1i56wrszhln4-facter-3.11.1
- directory tree listing: https://gist.github.com/10738b9674532db0804dfba417c5d454
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/fio/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6/bin/fio -h’ got 0 exit code
- ran ‘/nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6/bin/fio --help’ got 0 exit code
- ran ‘/nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6/bin/fio -v’ and found version 3.6
- ran ‘/nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6/bin/fio --version’ and found version 3.6
- ran ‘/nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6/bin/genfio -h’ got 0 exit code
- ran ‘/nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6/bin/genfio --help’ got 0 exit code
- ran ‘/nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6/bin/fiologparser.py -h’ got 0 exit code
- ran ‘/nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6/bin/fiologparser.py --help’ got 0 exit code
- ran ‘/nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6/bin/fio_jsonplus_clat2csv -h’ got 0 exit code
- ran ‘/nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6/bin/fio_jsonplus_clat2csv --help’ got 0 exit code
- found 3.6 with grep in /nix/store/vh0z8j2hhmcf5xwhhn0jagc2d213761g-fio-3.6
- directory tree listing: https://gist.github.com/0c7cb321a972c3e3e020645972a2d9f4
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/efivar/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/09zlj936d2jvjwdmj9c9f843fd86bcs3-efivar-35/bin/efivar -h’ got 0 exit code
- ran ‘/nix/store/09zlj936d2jvjwdmj9c9f843fd86bcs3-efivar-35/bin/efivar --help’ got 0 exit code
- ran ‘/nix/store/09zlj936d2jvjwdmj9c9f843fd86bcs3-efivar-35/bin/efivar help’ got 0 exit code
- found 35 with grep in /nix/store/09zlj936d2jvjwdmj9c9f843fd86bcs3-efivar-35
- directory tree listing: https://gist.github.com/6f811428a47ee181fc412ef78ff64450
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/di/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/lywps7y61srkjdi9pr5dv5dwjz8290mk-di-4.45/bin/mi -h’ got 0 exit code
- ran ‘/nix/store/lywps7y61srkjdi9pr5dv5dwjz8290mk-di-4.45/bin/mi --help’ got 0 exit code
- ran ‘/nix/store/lywps7y61srkjdi9pr5dv5dwjz8290mk-di-4.45/bin/di -h’ got 0 exit code
- ran ‘/nix/store/lywps7y61srkjdi9pr5dv5dwjz8290mk-di-4.45/bin/di --help’ got 0 exit code
- found 4.45 with grep in /nix/store/lywps7y61srkjdi9pr5dv5dwjz8290mk-di-4.45
- directory tree listing: https://gist.github.com/1cd553895ef02afdac0366bfee9f022e
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/efibootmgr/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/vfs7k6wfqa5xci24ckn8i28qkksw7wam-efibootmgr-16/bin/efibootdump --help’ got 0 exit code
- ran ‘/nix/store/vfs7k6wfqa5xci24ckn8i28qkksw7wam-efibootmgr-16/bin/efibootdump help’ got 0 exit code
- ran ‘/nix/store/vfs7k6wfqa5xci24ckn8i28qkksw7wam-efibootmgr-16/bin/efibootmgr -h’ got 0 exit code
- ran ‘/nix/store/vfs7k6wfqa5xci24ckn8i28qkksw7wam-efibootmgr-16/bin/efibootmgr --help’ got 0 exit code
- ran ‘/nix/store/vfs7k6wfqa5xci24ckn8i28qkksw7wam-efibootmgr-16/bin/efibootmgr help’ got 0 exit code
- ran ‘/nix/store/vfs7k6wfqa5xci24ckn8i28qkksw7wam-efibootmgr-16/bin/efibootmgr -V’ and found version 16
- ran ‘/nix/store/vfs7k6wfqa5xci24ckn8i28qkksw7wam-efibootmgr-16/bin/efibootmgr --version’ and found version 16
- found 16 with grep in /nix/store/vfs7k6wfqa5xci24ckn8i28qkksw7wam-efibootmgr-16
- directory tree listing: https://gist.github.com/d9d04d34e09782b7b051fbc60d7793aa
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/facter/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/azfbahp02g1xs110kvk4j281biimil8d-facter-3.11.0/bin/facter -h` got 0 exit code
- ran `/nix/store/azfbahp02g1xs110kvk4j281biimil8d-facter-3.11.0/bin/facter --help` got 0 exit code
- ran `/nix/store/azfbahp02g1xs110kvk4j281biimil8d-facter-3.11.0/bin/facter help` got 0 exit code
- ran `/nix/store/azfbahp02g1xs110kvk4j281biimil8d-facter-3.11.0/bin/facter -v` and found version 3.11.0
- ran `/nix/store/azfbahp02g1xs110kvk4j281biimil8d-facter-3.11.0/bin/facter --version` and found version 3.11.0
- found 3.11.0 with grep in /nix/store/azfbahp02g1xs110kvk4j281biimil8d-facter-3.11.0
- found 3.11.0 in filename of file in /nix/store/azfbahp02g1xs110kvk4j281biimil8d-facter-3.11.0
- directory tree listing: https://gist.github.com/f7f2e9775c3cd7188e8466f33d703e81
