When doing source routing/multihoming, it's practical to give names to routing
tables. The absence of the rt_table file in /etc make this impossible.
This patch recreates these files on rebuild so that they can be modified
by the user see NixOS#38638.
iproute2 is modified to look into config.networking.iproute2.confDir instead of
/etc/iproute2.
It turns out none of this stuff is needed. The docs aren't evenly built
properly anyways so the build trivially succeeds either way, due to what
looks like upstream misunderstanding automake. If I try to build the
docs manually in a cross shell (before and after this change), there's a
make rule error such that some HTML files aren't even attempted to be
built and then a copy fails.
Even if this was all fixed, these been a good number of cross fixes
upstream getting them to use CC_FOR_BUILD and other good stuff, so I
doubt such hacks would be needed.
Progress towards #40531 and #33302.
I’m not going to fix all of them but this is the best way to do this
in Apple things. Just add ‘EXPORT_DSTDIR’ to the installFlags & set
‘DSTDIR’ to $(out). Please do this instead of the patching!
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/alsa-utils/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecord -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecord --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsamixer -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsamixer --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsamixer help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amixer -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amixer --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amixer help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amixer -v’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amixer --version’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amidi -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amidi --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amidi -V’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/amidi --version’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplay -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplay --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/speaker-test -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/speaker-test --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaloop -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaloop --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsabat -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsabat --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplaymidi -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplaymidi --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplaymidi -V’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aplaymidi --version’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecordmidi -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecordmidi --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecordmidi -V’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/arecordmidi --version’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aseqdump -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aseqdump --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aseqdump -V’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/aseqdump --version’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaucm -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaucm --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaucm help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsatplg -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsatplg --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsa-info.sh -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsa-info.sh --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsa-info.sh help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaconf -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsaconf --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsactl -h’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsactl --help’ got 0 exit code
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsactl -v’ and found version 1.1.6
- ran ‘/nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6/bin/alsactl --version’ and found version 1.1.6
- found 1.1.6 with grep in /nix/store/kg9h54hxdg6hxs3agkfadacx5z8gaxiz-alsa-utils-1.1.6
- directory tree listing: https://gist.github.com/325af09e0dbb84a155838bdb37c5f89a
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pam_u2f/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/diyxvz87ashi10zx97b0dyl2hsr6f9bh-pam_u2f-1.0.6/bin/pamu2fcfg -h’ got 0 exit code
- ran ‘/nix/store/diyxvz87ashi10zx97b0dyl2hsr6f9bh-pam_u2f-1.0.6/bin/pamu2fcfg --help’ got 0 exit code
- ran ‘/nix/store/diyxvz87ashi10zx97b0dyl2hsr6f9bh-pam_u2f-1.0.6/bin/pamu2fcfg -V’ and found version 1.0.6
- ran ‘/nix/store/diyxvz87ashi10zx97b0dyl2hsr6f9bh-pam_u2f-1.0.6/bin/pamu2fcfg --version’ and found version 1.0.6
- found 1.0.6 with grep in /nix/store/diyxvz87ashi10zx97b0dyl2hsr6f9bh-pam_u2f-1.0.6
- directory tree listing: https://gist.github.com/7d4bb96a876d359bc67f88a024a674f8
Darling has a case conflict which means that its src hash will be
different between case sensitive and case insensitive file systems.
This is not ideal and the only way around it is basically to remove
the offending files from the output. I use fetchzip here to do that
but I hope there is a better fix available eventually.
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/kexec-tools/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/fs7vc5d6vw26v0502smh2dhg6390d1za-kexec-tools-2.0.17/bin/kexec -h’ got 0 exit code
- ran ‘/nix/store/fs7vc5d6vw26v0502smh2dhg6390d1za-kexec-tools-2.0.17/bin/kexec --help’ got 0 exit code
- ran ‘/nix/store/fs7vc5d6vw26v0502smh2dhg6390d1za-kexec-tools-2.0.17/bin/kexec -v’ and found version 2.0.17
- ran ‘/nix/store/fs7vc5d6vw26v0502smh2dhg6390d1za-kexec-tools-2.0.17/bin/kexec --version’ and found version 2.0.17
- found 2.0.17 with grep in /nix/store/fs7vc5d6vw26v0502smh2dhg6390d1za-kexec-tools-2.0.17
- directory tree listing: https://gist.github.com/892a831f872f6ec59c936b89b0bd6aa6
Adds a couple of useful NetBSD and OpenBSD derivations. Some of these
will be integrated into Nixpkgs later.
Noncomprehensive list:
- netbsd.getent
- netbsd.getconf
- netbsd.fts
- openbsd.mg
- netbsd.compat (can replace libbsd)
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/acpid/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpi_listen -h’ got 0 exit code
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpi_listen --help’ got 0 exit code
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpi_listen -v’ and found version 2.0.29
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpi_listen --version’ and found version 2.0.29
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpid help’ got 0 exit code
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpid -v’ and found version 2.0.29
- ran ‘/nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29/bin/acpid --version’ and found version 2.0.29
- found 2.0.29 with grep in /nix/store/vm7myzc830jgh1q5xmjc726xgw8fh933-acpid-2.0.29
- directory tree listing: https://gist.github.com/48210d03059b65f940b06df3ebb636d1
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mcelog/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/8dyjjqwjjhzsdfzk8sk0v2qj8b72gc5l-mcelog-157/bin/mcelog --help’ got 0 exit code
- ran ‘/nix/store/8dyjjqwjjhzsdfzk8sk0v2qj8b72gc5l-mcelog-157/bin/mcelog --version’ and found version 157
- found 157 with grep in /nix/store/8dyjjqwjjhzsdfzk8sk0v2qj8b72gc5l-mcelog-157
- directory tree listing: https://gist.github.com/cc3e7a088b51c408fc98ae7bba0d57c3
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pam_u2f/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/w4zrfq02p2ssbk391n380g8bm1fy8ai7-pam_u2f-1.0.5/bin/pamu2fcfg -h’ got 0 exit code
- ran ‘/nix/store/w4zrfq02p2ssbk391n380g8bm1fy8ai7-pam_u2f-1.0.5/bin/pamu2fcfg --help’ got 0 exit code
- ran ‘/nix/store/w4zrfq02p2ssbk391n380g8bm1fy8ai7-pam_u2f-1.0.5/bin/pamu2fcfg -V’ and found version 1.0.5
- ran ‘/nix/store/w4zrfq02p2ssbk391n380g8bm1fy8ai7-pam_u2f-1.0.5/bin/pamu2fcfg --version’ and found version 1.0.5
- found 1.0.5 with grep in /nix/store/w4zrfq02p2ssbk391n380g8bm1fy8ai7-pam_u2f-1.0.5
- directory tree listing: https://gist.github.com/63aa3c566fe3d6ad7704e45ee7e969fc
See:
https://github.com/NixOS/nixpkgs/issues/39154
Not sure why we're seeing that behavior re:fetchFromGitLab,
but for now use a likely-to-be-stable URL instead.
Fixes#39154.
(although the issue warrants some additional investigation IMO)
