Wireguard is now split into two pretty much independent packages:
`wireguard` (Linux-specific kernel module) and `wireguard-tools`,
which is cross-platform.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/usbutils/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/wgq4wwb9dxnhkbih9jscikf2lxhdvbkl-usbutils-010/bin/lsusb.py had a zero exit code or showed the expected version
- /nix/store/wgq4wwb9dxnhkbih9jscikf2lxhdvbkl-usbutils-010/bin/usbhid-dump passed the binary check.
- /nix/store/wgq4wwb9dxnhkbih9jscikf2lxhdvbkl-usbutils-010/bin/lsusb passed the binary check.
- /nix/store/wgq4wwb9dxnhkbih9jscikf2lxhdvbkl-usbutils-010/bin/usb-devices passed the binary check.
- 3 of 4 passed binary check by having a zero exit code.
- 1 of 4 passed binary check by having the new version present in output.
- found 010 with grep in /nix/store/wgq4wwb9dxnhkbih9jscikf2lxhdvbkl-usbutils-010
- directory tree listing: https://gist.github.com/ea1dc2aa0de1416d4359481ce7edb85e
- du listing: https://gist.github.com/f46f6ac9b995df459105446dc2761e28
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/firejail/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/5zjr9idl48c08apan8gh45wh971i49i9-firejail-0.9.54/bin/firejail had a zero exit code or showed the expected version
- /nix/store/5zjr9idl48c08apan8gh45wh971i49i9-firejail-0.9.54/bin/firemon passed the binary check.
- /nix/store/5zjr9idl48c08apan8gh45wh971i49i9-firejail-0.9.54/bin/firecfg passed the binary check.
- 2 of 3 passed binary check by having a zero exit code.
- 2 of 3 passed binary check by having the new version present in output.
- found 0.9.54 with grep in /nix/store/5zjr9idl48c08apan8gh45wh971i49i9-firejail-0.9.54
- directory tree listing: https://gist.github.com/3fb76054296d9e45fea3c47ae6a9f03f
- du listing: https://gist.github.com/a732bad0be0159f527ca4e8c532400ed
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)
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
