Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/nsd/versions.
These checks were done:
- built on NixOS
- /nix/store/vwidqdayh0l8rf5sjq37hr6ygdxrmkbb-nsd-4.1.21/bin/nsd passed the binary check.
- Warning: no invocation of /nix/store/vwidqdayh0l8rf5sjq37hr6ygdxrmkbb-nsd-4.1.21/bin/nsd-checkconf had a zero exit code or showed the expected version
- /nix/store/vwidqdayh0l8rf5sjq37hr6ygdxrmkbb-nsd-4.1.21/bin/nsd-checkzone passed the binary check.
- Warning: no invocation of /nix/store/vwidqdayh0l8rf5sjq37hr6ygdxrmkbb-nsd-4.1.21/bin/nsd-control had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/vwidqdayh0l8rf5sjq37hr6ygdxrmkbb-nsd-4.1.21/bin/nsd-control-setup had a zero exit code or showed the expected version
- 2 of 5 passed binary check by having a zero exit code.
- 0 of 5 passed binary check by having the new version present in output.
- found 4.1.21 with grep in /nix/store/vwidqdayh0l8rf5sjq37hr6ygdxrmkbb-nsd-4.1.21
- directory tree listing: https://gist.github.com/57f572db82ca8e038bcf1c970d13f10e
- du listing: https://gist.github.com/11c687e733f7222872d6e3733c5f9d0b
The hack of using `crossConfig` to enforce stricter handling of
dependencies is replaced with a dedicated `strictDeps` for that purpose.
(Experience has shown that my punning was a terrible idea that made more
difficult and embarrising to teach teach.)
Now that is is clear, a few packages now use `strictDeps`, to fix
various bugs:
- bintools-wrapper and cc-wrapper
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/osrm-backend/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-extract -h’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-extract --help’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-extract -v’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-extract --version’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-partition -h’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-partition --help’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-partition -v’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-partition --version’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-customize -h’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-customize --help’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-customize -v’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-customize --version’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-contract -h’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-contract --help’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-contract -v’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-contract --version’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-datastore -h’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-datastore --help’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-datastore -v’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-datastore --version’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-routed -h’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-routed --help’ got 0 exit code
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-routed -v’ and found version 5.18.0
- ran ‘/nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0/bin/osrm-routed --version’ and found version 5.18.0
- found 5.18.0 with grep in /nix/store/9qxw8mgxq15czqp580vwxwkc70mc3l2g-osrm-backend-5.18.0
- directory tree listing: https://gist.github.com/dfbc55be9a7c8ad0f9dc070af96865e2
- du listing: https://gist.github.com/8791bb0044495bd4d8dbf95ab3f97175
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/powerdns/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/pdns_control -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/pdns_control --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/pdnsutil -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/pdnsutil --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/pdnsutil help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/pdnsutil --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/zone2sql --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/zone2sql --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/zone2json --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/zone2json --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsgram -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsgram --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsgram help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsgram --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsreplay -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsreplay --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsreplay help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsreplay --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsscan -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsscan --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsscan help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsscan --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsscope -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsscope --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsscope help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsscope --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnswasher --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnswasher --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dumresp --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dumresp --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/pdns_notify --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/pdns_notify --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/nproxy -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/nproxy --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/nproxy --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/nsec3dig --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/nsec3dig --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/stubquery -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/stubquery --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/stubquery help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/stubquery --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/ixplore --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/ixplore --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/sdig --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/sdig --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/calidns -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/calidns --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/calidns --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsbulktest -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsbulktest --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnsbulktest --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnstcpbench -h’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnstcpbench --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnstcpbench --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/zone2ldap --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/zone2ldap --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnspcap2protobuf --help’ got 0 exit code
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/dnspcap2protobuf --version’ and found version 4.1.2
- ran ‘/nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2/bin/pdns_server --help’ got 0 exit code
- found 4.1.2 with grep in /nix/store/wc0f44gmgaxq2qh1w1x9k3i8z0z7i304-powerdns-4.1.2
- directory tree listing: https://gist.github.com/35d763a9dcfb4d88e41f300f06f27168
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/jackett/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/n7k1adzjashxif5k4m84ywij7bh2ck14-jackett-0.8.953/bin/Jackett -h’ got 0 exit code
- ran ‘/nix/store/n7k1adzjashxif5k4m84ywij7bh2ck14-jackett-0.8.953/bin/Jackett help’ got 0 exit code
- found 0.8.953 with grep in /nix/store/n7k1adzjashxif5k4m84ywij7bh2ck14-jackett-0.8.953
- directory tree listing: https://gist.github.com/32e346c875f3b936a083c815724f8a9f
Things done:
- use libGLU instead of mesa for darwin support
- move patches from local to github url
- fixup xquartz install
There may still be some issues at runtime. PRs welcome!
Fixes#40196
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/hiawatha/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/pk9y5j3rn2kh3jyh6shf16x7fwif5j8b-hiawatha-10.8.1/bin/ssi-cgi -h’ got 0 exit code
- ran ‘/nix/store/pk9y5j3rn2kh3jyh6shf16x7fwif5j8b-hiawatha-10.8.1/bin/ssi-cgi -v’ and found version 10.8.1
- ran ‘/nix/store/pk9y5j3rn2kh3jyh6shf16x7fwif5j8b-hiawatha-10.8.1/bin/hiawatha -h’ got 0 exit code
- ran ‘/nix/store/pk9y5j3rn2kh3jyh6shf16x7fwif5j8b-hiawatha-10.8.1/bin/wigwam -h’ got 0 exit code
- ran ‘/nix/store/pk9y5j3rn2kh3jyh6shf16x7fwif5j8b-hiawatha-10.8.1/bin/wigwam -v’ and found version 10.8.1
- found 10.8.1 with grep in /nix/store/pk9y5j3rn2kh3jyh6shf16x7fwif5j8b-hiawatha-10.8.1
- directory tree listing: https://gist.github.com/bed64b3bf49236cbbfafddbb1f63c00a
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/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/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
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/jackett/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/5zfami4c97mdgiw2kga88hbr050gz9nl-jackett-0.8.929/bin/Jackett -h’ got 0 exit code
- ran ‘/nix/store/5zfami4c97mdgiw2kga88hbr050gz9nl-jackett-0.8.929/bin/Jackett help’ got 0 exit code
- found 0.8.929 with grep in /nix/store/5zfami4c97mdgiw2kga88hbr050gz9nl-jackett-0.8.929
- directory tree listing: https://gist.github.com/abeee550859eff26afc80fcec3b0ec15
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
(cherry picked from commit ba52ae5048)
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
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/osrm-backend/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-extract -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-extract --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-extract -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-extract --version’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-partition -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-partition --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-partition -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-partition --version’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-customize -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-customize --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-customize -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-customize --version’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-contract -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-contract --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-contract -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-contract --version’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-datastore -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-datastore --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-datastore -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-datastore --version’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-routed -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-routed --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-routed -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-routed --version’ and found version 5.17.2
- found 5.17.2 with grep in /nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2
- directory tree listing: https://gist.github.com/82e852d822486a83285e755488f6d056
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/sabnzbd/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/rl41iqq34y5lbia598awnnr5zlqvn7p0-sabnzbd-2.3.3/bin/.sabnzbd-wrapped -h’ got 0 exit code
- ran ‘/nix/store/rl41iqq34y5lbia598awnnr5zlqvn7p0-sabnzbd-2.3.3/bin/.sabnzbd-wrapped --help’ got 0 exit code
- ran ‘/nix/store/rl41iqq34y5lbia598awnnr5zlqvn7p0-sabnzbd-2.3.3/bin/sabnzbd -h’ got 0 exit code
- ran ‘/nix/store/rl41iqq34y5lbia598awnnr5zlqvn7p0-sabnzbd-2.3.3/bin/sabnzbd --help’ got 0 exit code
- found 2.3.3 with grep in /nix/store/rl41iqq34y5lbia598awnnr5zlqvn7p0-sabnzbd-2.3.3
- directory tree listing: https://gist.github.com/06ad54e65a99a41896933852c69b59c1
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/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/foxx-manager --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/foxx-manager help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arangobench --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arangodump --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arangoexport --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arangoimp --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arangorestore --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arangosh --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arangovpack --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arango-dfdb --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arango-init-database --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arango-secure-installation --help’ got 0 exit code
- ran ‘/nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7/bin/arangod --help’ got 0 exit code
- found 3.3.7 with grep in /nix/store/lh49lm0kdkijvg9q9kzmacnclh5x2s4m-arangodb-3.3.7
- directory tree listing: https://gist.github.com/3fef3cf0eb3977fe8d69df9bbbedc5a9
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/freeradius/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radcrypt help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/smbencrypt -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/smbencrypt --help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/smbencrypt help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radsniff -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radlast -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radlast --help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radzap -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radiusd -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radmin -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/radmin --help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/rc.radiusd -h’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/rc.radiusd --help’ got 0 exit code
- ran ‘/nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17/bin/rc.radiusd help’ got 0 exit code
- found 3.0.17 with grep in /nix/store/w85s8cwg1d1kblhqiqi1fqxka1lilfb5-freeradius-3.0.17
- directory tree listing: https://gist.github.com/0674f9c9bf80af589d86399e508dc604
