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)
Source master rebase of my [PR #34].
Eventually, we might consider doing something for GNU binutils too, in
order that we switch (the normal) ld-wrapper to always use this to
leverage ld to resolve libraries, rather than faking it in bash.
[PR #34]: https://github.com/tpoechtrager/cctools-port/pull/34
During the last staging merge I assume that we turned on
-Werror=format-security by default (haven't checked in-depth though),
which actually is a good thing.
This causes the rtkit build to now fail, so I took a patch from Debian
to fix these issues.
Signed-off-by: aszlig <aszlig@nix.build>
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/ipset/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/p1k7d2y5aa4haxlkkn2jadviwvl5plcc-ipset-6.38/bin/ipset -h’ got 0 exit code
- ran ‘/nix/store/p1k7d2y5aa4haxlkkn2jadviwvl5plcc-ipset-6.38/bin/ipset --help’ got 0 exit code
- ran ‘/nix/store/p1k7d2y5aa4haxlkkn2jadviwvl5plcc-ipset-6.38/bin/ipset help’ got 0 exit code
- found 6.38 with grep in /nix/store/p1k7d2y5aa4haxlkkn2jadviwvl5plcc-ipset-6.38
- directory tree listing: https://gist.github.com/0c86d4251a82d41c7e788e320f7013d0
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/sysstat/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/sar --help’ got 0 exit code
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/iostat -h’ got 0 exit code
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/iostat help’ got 0 exit code
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/pidstat -h’ got 0 exit code
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/cifsiostat -h’ got 0 exit code
- ran ‘/nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3/bin/cifsiostat help’ got 0 exit code
- found 11.7.3 with grep in /nix/store/2f4cmqnz0wn43pyq8qnlb7pvhk3gh7bq-sysstat-11.7.3
- directory tree listing: https://gist.github.com/1274e29f5a0476b26643f85767b98e40
Otherwise the build system computes incorrect references and looks for
perf-core in /libexec. DESTDIR for normal buildsystems is never the
right choice for nixpkgs.
With #36556, a check was introduced to make sure the user and group
names do not exceed their respective maximum length. This is in part
because systemd also enforces that length, but only at runtime.
So in general it's a good idea to catch as much as we can during
evaluation time, however the maximum length of the group name was set to
16 characters according groupadd(8).
The maximum length of the group names however is a compile-time option
and even systemd allows more than 16 characters. In the mentioned pull
request (#36556) there was already a report that this has broken
evaluation for people out there.
I have also checked what other distributions are doing and they set the
length to either 31 characters or 32 characters, the latter being more
common.
Unfortunately there is a difference between the maximum length enforced
by the shadow package and systemd, both for user name lengths and group
name lengths. However, systemd enforces both length to have a maximum of
31 characters and I'm not sure if this is intended or just a off-by-one
error in systemd.
Nevertheless, I choose 32 characters simply to bring it in par with the
maximum user name length.
For the NixOS assertion however, I use a maximum length of 31 to make
sure that nobody accidentally creates services that contain group names
that systemd considers invalid because of a length of 32 characters.
Signed-off-by: aszlig <aszlig@nix.build>
Closes: #38548
Cc: @vcunat, @fpletz, @qknight
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-lib/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/37xgjr2ij3mvfrncywd23q2csnpbc1id-alsa-lib-1.1.6/bin/aserver -h’ got 0 exit code
- ran ‘/nix/store/37xgjr2ij3mvfrncywd23q2csnpbc1id-alsa-lib-1.1.6/bin/aserver --help’ got 0 exit code
- found 1.1.6 with grep in /nix/store/37xgjr2ij3mvfrncywd23q2csnpbc1id-alsa-lib-1.1.6
- directory tree listing: https://gist.github.com/9d2e30dc8cb0e3b643b48b4ddbe3a418
The required argument 'hostPlatform' was missing from linuxPackages_custom's
call to linuxManualConfig.
In order to prevent this in the future, this commit adds
linuxPackages_custom_tinyconfig_kernel so linuxPackages_custom gets tested.
This also adds linuxConfig, to derivate default linux configurations
via make defconfig, make tinyconfig, etc.
Closes#38034.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/lxc/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-attach -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-attach --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-attach --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-autostart -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-autostart --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-autostart --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-cgroup -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-cgroup --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-cgroup --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-checkpoint -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-checkpoint --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-checkpoint --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-copy -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-copy --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-copy --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-config -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-config --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-console -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-console --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-console --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-create -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-create --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-create --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-destroy -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-destroy --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-destroy --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-execute -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-execute --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-execute --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-freeze -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-freeze --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-freeze --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-info -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-info --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-info --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-ls -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-ls --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-ls help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-ls --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-monitor -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-monitor --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-monitor --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-snapshot -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-snapshot --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-snapshot --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-start -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-start --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-start --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-stop -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-stop --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-stop --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-top -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-top --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-top --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-unfreeze -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-unfreeze --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-unfreeze --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-unshare -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-unshare --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-unshare help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-usernsexec -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-wait -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-wait --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-wait --version’ and found version 3.0.0
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-checkconfig -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-checkconfig --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-checkconfig help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-update-config -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/lxc-update-config --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/init.lxc -h’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/init.lxc --help’ got 0 exit code
- ran ‘/nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0/bin/init.lxc --version’ and found version 3.0.0
- found 3.0.0 with grep in /nix/store/mvaxvwlslyaiksjrwcm2rmmnnf8z02w3-lxc-3.0.0
- directory tree listing: https://gist.github.com/a0534e4d403fd56527c3c04558911af3
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/sysvinit/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/n54idc6ddkgkwnbbg8y6avb5wvzb5s34-sysvinit-2.89/bin/last help` got 0 exit code
- ran `/nix/store/n54idc6ddkgkwnbbg8y6avb5wvzb5s34-sysvinit-2.89/bin/utmpdump -h` got 0 exit code
- ran `/nix/store/n54idc6ddkgkwnbbg8y6avb5wvzb5s34-sysvinit-2.89/bin/wall help` got 0 exit code
- found 2.89 with grep in /nix/store/n54idc6ddkgkwnbbg8y6avb5wvzb5s34-sysvinit-2.89
- directory tree listing: https://gist.github.com/6fdc40b90f12b6caa767385d367da4d9
Since at least d7bddc27b2, we've had a
situation where one should depend on:
- `stdenv.cc.bintools`: for executables at build time
- `libbfd` or `libiberty`: for those libraries
- `targetPackages.cc.bintools`: for exectuables at *run* time
- `binutils`: only for specifically GNU Binutils's executables,
regardless of the host platform, at run time.
and that commit cleaned up this usage to reflect that. This PR flips the
switch so that:
- `binutils` is indeed unconditionally GNU Binutils
- `binutils-raw`, which previously served that role, is gone.
so that the correct usage will be enforced going forward and everything
is simple.
N.B. In a few cases `binutils-unwrapped` (which before and now was
unconditionally actual GNU binutils), rather than `binutils` was used to
replace old `binutils-raw` as it is friendly towards some cross
compilation usage by avoiding a reference to the next bootstrapping
change.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/criu/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/yqfshz1c0qp2h8vdcswiaknxb6ibxfsl-criu-3.8.1/bin/compel -h` got 0 exit code
- ran `/nix/store/yqfshz1c0qp2h8vdcswiaknxb6ibxfsl-criu-3.8.1/bin/compel --help` got 0 exit code
- ran `/nix/store/yqfshz1c0qp2h8vdcswiaknxb6ibxfsl-criu-3.8.1/bin/criu -h` got 0 exit code
- ran `/nix/store/yqfshz1c0qp2h8vdcswiaknxb6ibxfsl-criu-3.8.1/bin/criu --help` got 0 exit code
- ran `/nix/store/yqfshz1c0qp2h8vdcswiaknxb6ibxfsl-criu-3.8.1/bin/criu -V` and found version 3.8.1
- ran `/nix/store/yqfshz1c0qp2h8vdcswiaknxb6ibxfsl-criu-3.8.1/bin/criu --version` and found version 3.8.1
- found 3.8.1 with grep in /nix/store/yqfshz1c0qp2h8vdcswiaknxb6ibxfsl-criu-3.8.1
- directory tree listing: https://gist.github.com/4324a1815464a7da41c4b8cd5056b1b7
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/sysdig/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/sysdig -h` got 0 exit code
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/sysdig --help` got 0 exit code
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/sysdig help` got 0 exit code
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/sysdig --version` and found version 0.21.0
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/sysdig -h` and found version 0.21.0
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/sysdig --help` and found version 0.21.0
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/csysdig -h` got 0 exit code
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/csysdig --help` got 0 exit code
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/csysdig help` got 0 exit code
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/csysdig -V` and found version 0.21.0
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/csysdig -v` and found version 0.21.0
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/csysdig --version` and found version 0.21.0
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/csysdig -h` and found version 0.21.0
- ran `/nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0/bin/csysdig --help` and found version 0.21.0
- found 0.21.0 with grep in /nix/store/q46s7qx6pq8wlwqgi6dcdjcb41qc0zn9-sysdig-0.21.0
- directory tree listing: https://gist.github.com/90f767f238a59aa31ac34058784510d7
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/fwts/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/vvq9vagwr2qzs3xg1ssrkpbiwk6ayq2c-fwts-18.03.00/bin/fwts -h` got 0 exit code
- ran `/nix/store/vvq9vagwr2qzs3xg1ssrkpbiwk6ayq2c-fwts-18.03.00/bin/fwts --help` got 0 exit code
- ran `/nix/store/vvq9vagwr2qzs3xg1ssrkpbiwk6ayq2c-fwts-18.03.00/bin/fwts -V` and found version 18.03.00
- ran `/nix/store/vvq9vagwr2qzs3xg1ssrkpbiwk6ayq2c-fwts-18.03.00/bin/fwts -v` and found version 18.03.00
- ran `/nix/store/vvq9vagwr2qzs3xg1ssrkpbiwk6ayq2c-fwts-18.03.00/bin/fwts --version` and found version 18.03.00
- ran `/nix/store/vvq9vagwr2qzs3xg1ssrkpbiwk6ayq2c-fwts-18.03.00/bin/fwts -h` and found version 18.03.00
- ran `/nix/store/vvq9vagwr2qzs3xg1ssrkpbiwk6ayq2c-fwts-18.03.00/bin/fwts --help` and found version 18.03.00
- found 18.03.00 with grep in /nix/store/vvq9vagwr2qzs3xg1ssrkpbiwk6ayq2c-fwts-18.03.00
- directory tree listing: https://gist.github.com/cf8ebe142dd89bc324517d19193e70f4
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/hdparm/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/c646kg7w31rm3rz30n145jf77kjw2dmg-hdparm-9.56/bin/hdparm -h` got 0 exit code
- ran `/nix/store/c646kg7w31rm3rz30n145jf77kjw2dmg-hdparm-9.56/bin/hdparm -V` and found version 9.56
- ran `/nix/store/c646kg7w31rm3rz30n145jf77kjw2dmg-hdparm-9.56/bin/hdparm -h` and found version 9.56
- found 9.56 with grep in /nix/store/c646kg7w31rm3rz30n145jf77kjw2dmg-hdparm-9.56
- directory tree listing: https://gist.github.com/288d8bff26d3af52b38fbd8055ee2aac
OpenSMTPD does not require the setuid bit for its `sendmail`. This works
around it by wrapping the called `sendmail` so that the wrapper falls
back on either the setuid `sendmail` or the non-setuid `sendmail`
depending on what's available.
The solution of relying on `$PATH` to be set is unfortunately
unreliable, as `mdadm --monitor` will likely be executed from a
`systemd` unit, that runs with a clean `$PATH`.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/i2c-tools/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-dimms -h` got 0 exit code
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-dimms --help` got 0 exit code
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-dimms help` got 0 exit code
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-dimms -h` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-dimms --help` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-vaio -h` got 0 exit code
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-vaio --help` got 0 exit code
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-vaio help` got 0 exit code
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-edid -h` got 0 exit code
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-edid --help` got 0 exit code
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-edid help` got 0 exit code
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-edid -V` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-edid -v` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-edid --version` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-edid version` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-edid -h` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-edid --help` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/decode-edid help` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/i2cdetect -V` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/i2cdump -V` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/i2cget -V` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/i2cset -V` and found version 4.0
- ran `/nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0/bin/i2ctransfer -V` and found version 4.0
- found 4.0 with grep in /nix/store/01psgfkqwlff69addbhp08xi5z2p3y7w-i2c-tools-4.0
- directory tree listing: https://gist.github.com/7e7d303f66bb0a865a35ab286258a07e
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/bluez/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluetoothctl -h` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluetoothctl --help` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluetoothctl help` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluetoothctl -V` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluetoothctl -v` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluetoothctl --version` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluetoothctl version` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluetoothctl -h` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluetoothctl --help` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/btmon -h` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/btmon --help` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/btmon -v` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/btmon --version` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bccmd -h` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bccmd --help` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bccmd -V` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bccmd -v` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bccmd --version` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluemoon -h` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluemoon --help` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluemoon -v` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/bluemoon --version` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/hex2hcd -h` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/hex2hcd --help` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/hex2hcd help` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/hex2hcd -v` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/hex2hcd --version` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/mpris-proxy -h` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/mpris-proxy --help` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/mpris-proxy -v` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/mpris-proxy --version` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/btattach -h` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/btattach --help` got 0 exit code
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/btattach -v` and found version 5.49
- ran `/nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49/bin/btattach --version` and found version 5.49
- found 5.49 with grep in /nix/store/il6jjsm4s96wn87y7jalbsasnh70f2gx-bluez-5.49
- directory tree listing: https://gist.github.com/29a23518ac04729281c02f4a2e81e310
The isSeccomputable flag treated Linux without seccomp as just a
normal variant, when it really should be treated as a special case
incurring complexity debt to support.
The isKexecable flag treated Linux without kexec as just a normal
variant, when it really should be treated as a special case incurring
complexity debt to support.
* Implement libGL as a symlink package which uses libraries from libglvnd and
headers from Mesa (since ones from libglvnd are outdated).
* Use libGL_driver.driverLink treewide; add FHS paths where possible.
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 4.8 with grep in /nix/store/lbmm10zm3yif6n33xvw5irzhzsqkwk7b-pam-krb5-4.8
- directory tree listing: https://gist.github.com/8511cb10102508ce5701ed7e0830e60c
