Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/cmark/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/ws8c9r62c7wsas7kj1v0svfs57d53dvv-cmark-0.28.3/bin/cmark -h’ got 0 exit code
- ran ‘/nix/store/ws8c9r62c7wsas7kj1v0svfs57d53dvv-cmark-0.28.3/bin/cmark --help’ got 0 exit code
- found 0.28.3 with grep in /nix/store/ws8c9r62c7wsas7kj1v0svfs57d53dvv-cmark-0.28.3
- directory tree listing: https://gist.github.com/890d356ed9766b2fca77baebee346a0e
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/cppcheck/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/naming.py -h’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/naming.py --help’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/naming.py help’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/y2038.py -h’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/y2038.py --help’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/y2038.py help’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/cppcheck -h’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/cppcheck --help’ got 0 exit code
- ran ‘/nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83/bin/cppcheck --version’ and found version 1.83
- found 1.83 with grep in /nix/store/y9shqxbgyq6g7v5vx76f69901yb8sj06-cppcheck-1.83
- directory tree listing: https://gist.github.com/49acebba8d7d9e3af647133ae23bd1cb
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/containerd/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/containerd -h’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/containerd --help’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/containerd help’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/containerd-release -h’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/containerd-release --help’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/containerd-release help’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/containerd-stress -h’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/containerd-stress --help’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/containerd-stress help’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/ctr -h’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/ctr --help’ got 0 exit code
- ran ‘/nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3/bin/ctr help’ got 0 exit code
- found 1.0.3 with grep in /nix/store/qmgzfad2cazgv7j1k31pqs512b59b8hp-containerd-1.0.3
- directory tree listing: https://gist.github.com/b830fb8c24834f83e627fd6d567eae87
Setting the hash to null is a convenient way to bypass the hash check
while developing. It looks like the ability to do this was inadvertently
removed while adding vendor directory support.
This still checks that the user is explicitly setting the value but
allows null as a valid option.
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/getmail/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail-wrapped -h’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail-wrapped --help’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail-wrapped --version’ and found version 5.6
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail -h’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail --help’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail --version’ and found version 5.6
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail-gmail-xoauth-tokens-wrapped -h’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail-gmail-xoauth-tokens-wrapped --help’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail-gmail-xoauth-tokens -h’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail-gmail-xoauth-tokens --help’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail_fetch-wrapped -h’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail_fetch-wrapped --help’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail_fetch-wrapped --version’ and found version 5.6
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail_fetch -h’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail_fetch --help’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail_fetch --version’ and found version 5.6
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail_maildir-wrapped -h’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail_maildir-wrapped --help’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail_maildir -h’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail_maildir --help’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail_mbox-wrapped -h’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/.getmail_mbox-wrapped --help’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail_mbox -h’ got 0 exit code
- ran ‘/nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6/bin/getmail_mbox --help’ got 0 exit code
- found 5.6 with grep in /nix/store/m5b7cgi58ahzp7n1j6x7gjxjm77fsj9i-getmail-5.6
- directory tree listing: https://gist.github.com/05a73027c43a157053c33c4886d466f8
This allows the lib fixed point to be extended with
myLib = lib.extend (self: super: {
foo = "foo";
})
With this it's possible to have the new modified lib attrset available to all
modules when using evalModules
myLib.evalModules {
modules = [ ({ lib, ... }: {
options.bar = lib.mkOption {
default = lib.foo;
};
}) ];
}
=> { config = { bar = "foo"; ... }; options = ...; }
This patch is heavily inspired by bd0d8ed807 which added
a setcap wrapper for `mtr` in order to allow running `mtr` without
`sudo`. The need for the capability `cap_net_raw` that can be registered using
`setcap` has been documented in the Arch Wiki: https://wiki.archlinux.org/index.php/Capabilities#iftop
A simple testcase has been added which starts two machines, one with a
setcap wrapper for `iftop`, one without. Both testcases monitor the
bandwidth usage of the machine using the options `-t -s 1` once, the
machine with setcap wrapper is expected to succeed, the `iftop` on the
machine without setcap wrapper is expected to return a non-zero exit
code.
Upstream requested that we remove these packages until the first stable
release. More details are in #38344. This isn't ideal but it seems like
the best solution for now.
Close#38344.
R. RyanTM