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/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
