Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/arangodb/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/foxx-manager --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/foxx-manager help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arangobench --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arangodump --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arangoexport --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arangoimp --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arangorestore --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arangosh --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arangovpack --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arango-dfdb --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arango-init-database --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arango-secure-installation --help’ got 0 exit code
- ran ‘/nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8/bin/arangod --help’ got 0 exit code
- found 3.3.8 with grep in /nix/store/9v5zwlwxxk5akankjbrspij0r495izy7-arangodb-3.3.8
- directory tree listing: https://gist.github.com/bf252dfee33f01f0180733cc37983efd
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/zookeeper/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/g0fmbsp2n6sgh4fa9k6w2m3ndq9vhcxl-zookeeper-3.4.12/bin/zkServer.sh -h’ got 0 exit code
- ran ‘/nix/store/g0fmbsp2n6sgh4fa9k6w2m3ndq9vhcxl-zookeeper-3.4.12/bin/zkServer.sh --help’ got 0 exit code
- ran ‘/nix/store/g0fmbsp2n6sgh4fa9k6w2m3ndq9vhcxl-zookeeper-3.4.12/bin/zkServer.sh help’ got 0 exit code
- ran ‘/nix/store/g0fmbsp2n6sgh4fa9k6w2m3ndq9vhcxl-zookeeper-3.4.12/bin/zkCli.sh help’ got 0 exit code
- found 3.4.12 with grep in /nix/store/g0fmbsp2n6sgh4fa9k6w2m3ndq9vhcxl-zookeeper-3.4.12
- directory tree listing: https://gist.github.com/9a91124b15dbb7aa6469746b3edb67a9
Ubiquiti has both a LTS and current version of their Unifi controller software.
The latter adds new features, but may drop support for some devices.
This adds the capability to use either for the unifi module but defaults
to the LTS version, which was the previous behavior.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/radicale/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/rbymr2y0pbx8n8b8bfz2gscafmby904x-radicale-2.1.9/bin/.radicale-wrapped -h’ got 0 exit code
- ran ‘/nix/store/rbymr2y0pbx8n8b8bfz2gscafmby904x-radicale-2.1.9/bin/.radicale-wrapped --help’ got 0 exit code
- ran ‘/nix/store/rbymr2y0pbx8n8b8bfz2gscafmby904x-radicale-2.1.9/bin/.radicale-wrapped --version’ and found version 2.1.9
- ran ‘/nix/store/rbymr2y0pbx8n8b8bfz2gscafmby904x-radicale-2.1.9/bin/radicale -h’ got 0 exit code
- ran ‘/nix/store/rbymr2y0pbx8n8b8bfz2gscafmby904x-radicale-2.1.9/bin/radicale --help’ got 0 exit code
- ran ‘/nix/store/rbymr2y0pbx8n8b8bfz2gscafmby904x-radicale-2.1.9/bin/radicale --version’ and found version 2.1.9
- found 2.1.9 with grep in /nix/store/rbymr2y0pbx8n8b8bfz2gscafmby904x-radicale-2.1.9
- directory tree listing: https://gist.github.com/e41acc1e5d5f2db9d8498cf5a989eb7f
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
