Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/jhiccup/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/di6qgm16dycmq6xg4jhwbmin207kykkr-jhiccup-2.0.9/bin/jHiccup had a zero exit code or showed the expected version
- /nix/store/di6qgm16dycmq6xg4jhwbmin207kykkr-jhiccup-2.0.9/bin/jHiccupLogProcessor passed the binary check.
- 1 of 2 passed binary check by having a zero exit code.
- 0 of 2 passed binary check by having the new version present in output.
- found 2.0.9 with grep in /nix/store/di6qgm16dycmq6xg4jhwbmin207kykkr-jhiccup-2.0.9
- directory tree listing: https://gist.github.com/83abe7e20b3fd3db4dd38e3223479de0
- du listing: https://gist.github.com/196b47d4bb8d9ecf736bb2a7be08ce2c
The original `nexus` derivation required `/run/sonatype-work/nexus3`
which explicitly depended on the NixOS path structure.
This would break `nexus` for everyone using `nixpkgs` on a non-NixOS
system, additionally the module never created `/run/sonatype-work`, so
the systemd unit created in `services.nexus` fails as well. The issue
wasn't actively known as the `nixos/nexus` test wasn't registered in
Hydra (see #40257).
This patch contains the following changes:
* Adds `tests.nexus` to `release.nix` to run the test on Hydra.
* Makes JVM parameters configurable: by default all JVM options were located
in `result/bin/nexus.vmoptions` which made it quite hard to patch
these parameters. Now it's possible to override all parameters by
running `VM_OPTS_FILE=custom-nexus.vmoptions ./result/bin/nexus run`
(after patching the `nexus` shell script), additionally it's possible
to override these parameters with `services.nexus.vmoptions`.
* Bumped Nexus from 3.5.1 to 3.11.0
* Run the `nexus` test on Hydra with `callTest` in `nixos/release.nix`,
furthermore the test checks if the UI is available on the specified
port.
* Added myself as maintainer for the NixOS test and the package to have
some more people in case of further breakage.
* Added sufficient disk space to the `nexus` test, otherwise the service
fails with the following errors:
```
com.orientechnologies.orient.core.exception.ODatabaseException: Cannot create database 'accesslog'
com.orientechnologies.orient.core.exception.OLowDiskSpaceException: Error occurred while executing
a write operation to database 'accesslog' due to limited free space on the disk (242 MB). The database
is now working in read-only mode. Please close the database (or stop OrientDB), make room on your hard
drive and then reopen the database. The minimal required space is 256 MB. Required space is now set to
256MB (you can change it by setting parameter storage.diskCache.diskFreeSpaceLimit) .
```
/cc @ironpinguin @xeji
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
And there's more reverts too. The previous commmit
d838afbc9376bdadb8c690eb00b425f3eeccdf2d to gnu-config finally solves
it!
This reverts commit 3ed545ab31.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/flow/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/sxq54vh13q17bn31lsz9gszx4abr8qcc-flow-0.72.0/bin/flow --help’ got 0 exit code
- ran ‘/nix/store/sxq54vh13q17bn31lsz9gszx4abr8qcc-flow-0.72.0/bin/flow version’ and found version 0.72.0
- found 0.72.0 with grep in /nix/store/sxq54vh13q17bn31lsz9gszx4abr8qcc-flow-0.72.0
- directory tree listing: https://gist.github.com/cf04036cc5756f0589397f496e3e5e87
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/remarshal/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2json-wrapped -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2json-wrapped --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2json-wrapped -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2json-wrapped --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2json -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2json --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2json -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2json --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2toml-wrapped -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2toml-wrapped --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2toml-wrapped -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2toml-wrapped --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2toml -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2toml --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2toml -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2toml --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2yaml-wrapped -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2yaml-wrapped --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2yaml-wrapped -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.json2yaml-wrapped --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2yaml -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2yaml --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2yaml -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/json2yaml --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.remarshal-wrapped -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.remarshal-wrapped --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.remarshal-wrapped -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.remarshal-wrapped --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/remarshal -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/remarshal --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/remarshal -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/remarshal --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2json-wrapped -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2json-wrapped --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2json-wrapped -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2json-wrapped --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2json -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2json --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2json -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2json --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2toml-wrapped -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2toml-wrapped --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2toml-wrapped -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2toml-wrapped --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2toml -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2toml --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2toml -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2toml --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2yaml-wrapped -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2yaml-wrapped --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2yaml-wrapped -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.toml2yaml-wrapped --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2yaml -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2yaml --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2yaml -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/toml2yaml --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2json-wrapped -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2json-wrapped --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2json-wrapped -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2json-wrapped --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2json -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2json --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2json -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2json --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2toml-wrapped -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2toml-wrapped --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2toml-wrapped -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2toml-wrapped --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2toml -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2toml --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2toml -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2toml --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2yaml-wrapped -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2yaml-wrapped --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2yaml-wrapped -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/.yaml2yaml-wrapped --version’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2yaml -h’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2yaml --help’ got 0 exit code
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2yaml -v’ and found version 0.8.0
- ran ‘/nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0/bin/yaml2yaml --version’ and found version 0.8.0
- found 0.8.0 with grep in /nix/store/8cafzxn7ffa6kzy55xf7y0hslgwnn4br-remarshal-0.8.0
- directory tree listing: https://gist.github.com/8dc1ba1b525a1d9d051b9cbbbf7fbe08
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/rust-bindgen/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/vpn165c8nv09k30dsl7gx0crzbdzw4im-rust-bindgen-0.36.1/bin/bindgen -h’ got 0 exit code
- ran ‘/nix/store/vpn165c8nv09k30dsl7gx0crzbdzw4im-rust-bindgen-0.36.1/bin/bindgen --help’ got 0 exit code
- ran ‘/nix/store/vpn165c8nv09k30dsl7gx0crzbdzw4im-rust-bindgen-0.36.1/bin/bindgen -V’ and found version 0.36.1
- ran ‘/nix/store/vpn165c8nv09k30dsl7gx0crzbdzw4im-rust-bindgen-0.36.1/bin/bindgen --version’ and found version 0.36.1
- found 0.36.1 with grep in /nix/store/vpn165c8nv09k30dsl7gx0crzbdzw4im-rust-bindgen-0.36.1
- directory tree listing: https://gist.github.com/6731d17415819fe988768028fda0e150
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/cfr/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/8hlizlz9d6cp6n3w3qx7s0wm2z3d3g8f-cfr-0.128/bin/cfr -h’ got 0 exit code
- ran ‘/nix/store/8hlizlz9d6cp6n3w3qx7s0wm2z3d3g8f-cfr-0.128/bin/cfr --help’ got 0 exit code
- ran ‘/nix/store/8hlizlz9d6cp6n3w3qx7s0wm2z3d3g8f-cfr-0.128/bin/cfr help’ got 0 exit code
- found 0.128 with grep in /nix/store/8hlizlz9d6cp6n3w3qx7s0wm2z3d3g8f-cfr-0.128
- directory tree listing: https://gist.github.com/3d40ccd7bfb3d81eb71e8a9033d1a127
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/fswatch/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/bin/fswatch -h’ got 0 exit code
- ran ‘/nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/bin/fswatch --help’ got 0 exit code
- found 1.11.3 with grep in /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3
- directory tree listing: https://gist.github.com/cc22e26348bfd98159c6519a470d3bdb
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mypy/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.dmypy-wrapped -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.dmypy-wrapped --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.dmypy-wrapped help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/dmypy -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/dmypy --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/dmypy help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.mypy-wrapped -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.mypy-wrapped --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.mypy-wrapped -V’ and found version 0.600
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.mypy-wrapped --version’ and found version 0.600
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/mypy -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/mypy --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/mypy -V’ and found version 0.600
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/mypy --version’ and found version 0.600
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.stubgen-wrapped -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.stubgen-wrapped --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/.stubgen-wrapped help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/stubgen -h’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/stubgen --help’ got 0 exit code
- ran ‘/nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600/bin/stubgen help’ got 0 exit code
- found 0.600 with grep in /nix/store/vzgfxa5pw3dprk1afv5r55kzhld2bkhw-mypy-0.600
- directory tree listing: https://gist.github.com/157118da991905110fee19075e61f99b
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/apktool/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool -h’ got 0 exit code
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool --help’ got 0 exit code
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool help’ got 0 exit code
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool --version’ and found version 2.3.3
- found 2.3.3 with grep in /nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3
- directory tree listing: https://gist.github.com/442f8aae9c8a9a0f7594fc049c97fe51
For details on the patches applied, see:
https://sources.debian.org/patches/ltrace/0.7.3-6/
Disabling '-Werror' may be a problem in the future again,
but for now keep things simple now that they're fixed.
Apparently, without this patch `NT_PRSTATUS` is not found. So the patch
adds the include apparently necessary. `NT_PRSTATUS` is also defined in
`<linux/ptrace.h>`, which would likely have been a better name, were it
not in the `linux/` directory, which is a priori not stable.
The need to do that is kind of weird (the change was introduced in [1],
and fedora apparently didn't need this additional import), but I'll try
to upstream it.
[1] https://github.com/SimonKagstrom/kcov/pull/239
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
On GNU/Linux the build references these files, so let's fetch them from
the Chromium repository. I haven't checked whether they are heavily
patched or whether we can use the version from LLVM, but when looking at
the changes, they do seem to divert a bit from upstream LLVM.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @matthewbauer, @stesie
The tarball from upstream seems to be generated on the fly, so the
output is not deterministic and using fetchzip makes this more reliable
as we have a recursively hashed output path without any of the
non-determinisms in tarballs.
Unfortunately, the build still fails on NixOS systems, because we need a
few more stuff in the build tree.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @matthewbauer, @stesie
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/chromedriver/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/bnjr4qgd68lh8fdz2hxz7qrc1zvvxkni-chromedriver-2.38/bin/chromedriver -h’ got 0 exit code
- ran ‘/nix/store/bnjr4qgd68lh8fdz2hxz7qrc1zvvxkni-chromedriver-2.38/bin/chromedriver --help’ got 0 exit code
- found 2.38 with grep in /nix/store/bnjr4qgd68lh8fdz2hxz7qrc1zvvxkni-chromedriver-2.38
- directory tree listing: https://gist.github.com/8ba491f60826e1ad2389e69f92fb6116
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/jbake/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/l85kq1n5mv8shw19rd26vx1qh2q2xj98-jbake-2.6.1/bin/jbake -h’ got 0 exit code
- ran ‘/nix/store/l85kq1n5mv8shw19rd26vx1qh2q2xj98-jbake-2.6.1/bin/jbake --help’ got 0 exit code
- ran ‘/nix/store/l85kq1n5mv8shw19rd26vx1qh2q2xj98-jbake-2.6.1/bin/jbake help’ got 0 exit code
- found 2.6.1 with grep in /nix/store/l85kq1n5mv8shw19rd26vx1qh2q2xj98-jbake-2.6.1
- directory tree listing: https://gist.github.com/27e3a60a9041b9898ce150344a6c3db4
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mypy/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/.dmypy-wrapped -h’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/.dmypy-wrapped --help’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/.dmypy-wrapped help’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/dmypy -h’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/dmypy --help’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/dmypy help’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/.mypy-wrapped -h’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/.mypy-wrapped --help’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/.mypy-wrapped -V’ and found version 0.590
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/.mypy-wrapped --version’ and found version 0.590
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/mypy -h’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/mypy --help’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/mypy -V’ and found version 0.590
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/mypy --version’ and found version 0.590
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/.stubgen-wrapped -h’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/.stubgen-wrapped --help’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/.stubgen-wrapped help’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/stubgen -h’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/stubgen --help’ got 0 exit code
- ran ‘/nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590/bin/stubgen help’ got 0 exit code
- found 0.590 with grep in /nix/store/949glp2ll51fziqzy2xnma6zvvn6ihlq-mypy-0.590
- directory tree listing: https://gist.github.com/28a5c2600f864ea85373e565ced612c6
This has already been patched against gnumake4 (519f0b8db2)
but we still have packages depending on gnumake3, so let's also apply
the same patch to gnumake 3.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @shlevy, @vcunat
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/apktool/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/dhjjw9xk7rx4gm6ngpgbf5kdhcgaxdgw-apktool-2.3.2/bin/apktool -h’ got 0 exit code
- ran ‘/nix/store/dhjjw9xk7rx4gm6ngpgbf5kdhcgaxdgw-apktool-2.3.2/bin/apktool --help’ got 0 exit code
- ran ‘/nix/store/dhjjw9xk7rx4gm6ngpgbf5kdhcgaxdgw-apktool-2.3.2/bin/apktool help’ got 0 exit code
- ran ‘/nix/store/dhjjw9xk7rx4gm6ngpgbf5kdhcgaxdgw-apktool-2.3.2/bin/apktool --version’ and found version 2.3.2
- found 2.3.2 with grep in /nix/store/dhjjw9xk7rx4gm6ngpgbf5kdhcgaxdgw-apktool-2.3.2
- directory tree listing: https://gist.github.com/7989c4dc760bbeb74791e11fb1bbebb1
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/strace/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/x7d4g7rvf9z43xjz7mc8c4nzwphghjj7-strace-4.22/bin/strace -h’ got 0 exit code
- ran ‘/nix/store/x7d4g7rvf9z43xjz7mc8c4nzwphghjj7-strace-4.22/bin/strace-log-merge -h’ got 0 exit code
- ran ‘/nix/store/x7d4g7rvf9z43xjz7mc8c4nzwphghjj7-strace-4.22/bin/strace-log-merge --help’ got 0 exit code
- ran ‘/nix/store/x7d4g7rvf9z43xjz7mc8c4nzwphghjj7-strace-4.22/bin/strace-log-merge help’ got 0 exit code
- found 4.22 with grep in /nix/store/x7d4g7rvf9z43xjz7mc8c4nzwphghjj7-strace-4.22
- directory tree listing: https://gist.github.com/4c8ab8738133d11c611ae7290d25d6fc
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/cppcheck/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/naming.py -h’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/naming.py --help’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/naming.py help’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/y2038.py -h’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/y2038.py --help’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/y2038.py help’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/cppcheck -h’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/cppcheck --help’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/cppcheck --version’ and found version 1.83
- found 1.83 with grep in /nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83
- directory tree listing: https://gist.github.com/49acebba8d7d9e3af647133ae23bd1cb
With this patch I remove myself as a maintainer for all packages I
currently maintain.
This is due the fact that I will be basically off the grid from May 2018
until early 2019, as I will be on a trip through north america.
I will revert this patch as soon as I'm back, as I plan to continue
contributing to nixpkgs then.
But as I cannot maintain anything during that time, I'd like to get this
patch merged.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/sysbench/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/d3633p13b97v5r5xswf85v9fxql1jv72-sysbench-1.0.14/bin/sysbench --help’ got 0 exit code
- ran ‘/nix/store/d3633p13b97v5r5xswf85v9fxql1jv72-sysbench-1.0.14/bin/sysbench --version’ and found version 1.0.14
- found 1.0.14 with grep in /nix/store/d3633p13b97v5r5xswf85v9fxql1jv72-sysbench-1.0.14
- directory tree listing: https://gist.github.com/56c18be2af370efb1c887dd27074fd4e
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/lttng-tools/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3/bin/lttng -V` and found version 2.10.3
- ran `/nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3/bin/lttng --version` and found version 2.10.3
- ran `/nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3/bin/lttng version` and found version 2.10.3
- ran `/nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3/bin/lttng-crash -V` and found version 2.10.3
- ran `/nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3/bin/lttng-crash --version` and found version 2.10.3
- found 2.10.3 with grep in /nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3
- directory tree listing: https://gist.github.com/bf4b92fc08881141af11b0444ed15630
