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/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
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.
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/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/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
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/babeltrace/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace -h` got 0 exit code
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace --help` got 0 exit code
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace -h` and found version 1.5.5
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace --help` and found version 1.5.5
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace-log -h` got 0 exit code
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace-log -h` and found version 1.5.5
- found 1.5.5 with grep in /nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5
- directory tree listing: https://gist.github.com/d849a2026946a7542bc3e2e6a586d713
Uses the HTTPS url for cases where the existing URL has a permanent
redirect. For each domain, at least one fixed derivation URL was
downloaded to test the domain is properly serving downloads.
Also fixes jbake source URL, which was broken.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks --help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks --version` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks --help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-5.1 --help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-5.1 help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-5.1 --version` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-5.1 --help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-5.1 help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin --help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin --version` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin --help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin-5.1 --help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin-5.1 help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin-5.1 --version` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin-5.1 --help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin-5.1 help` and found version 2.4.4
- found 2.4.4 with grep in /nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4
- directory tree listing: https://gist.github.com/cb3889fda28e8066faebd32a433c69d2
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 2018.03.13 with grep in /nix/store/gpwn8923mppc2h6vx2rgg8q52ss2mg2l-autoconf-archive-2018.03.13
- directory tree listing: https://gist.github.com/eaaa4f78b6bd461710c33aea9e21fdea
- The patch has been applied upstream.
- LSOF_INCLUDE was referring to wrong output, this broke the build.
- Remove an unneeded legacy sed.
- Maintain, while at it.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4/bin/itstool -h` got 0 exit code
- ran `/nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4/bin/itstool --help` got 0 exit code
- ran `/nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4/bin/itstool -v` and found version 2.0.4
- ran `/nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4/bin/itstool --version` and found version 2.0.4
- found 2.0.4 with grep in /nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4
- found 2.0.4 in filename of file in /nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/igt_stats -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/igt_stats --help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/igt_stats help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_reg --help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_reg help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_forcewaked -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_firmware_decode help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_gpu_top -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_gpu_top -h` and found version 1.22
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_guc_logger -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_guc_logger --help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_opregion_decode -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_opregion_decode --help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_dump_decode help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_error_decode help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_dp_compliance -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_dp_compliance --help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_dp_compliance -h` and found version 1.22
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_dp_compliance --help` and found version 1.22
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_aubdump -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_aubdump --help` got 0 exit code
- found 1.22 with grep in /nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22
- found 1.22 in filename of file in /nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22
Resolved the following conflicts (by carefully applying patches from the both
branches since the fork point):
pkgs/development/libraries/epoxy/default.nix
pkgs/development/libraries/gtk+/3.x.nix
pkgs/development/python-modules/asgiref/default.nix
pkgs/development/python-modules/daphne/default.nix
pkgs/os-specific/linux/systemd/default.nix
