After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.
Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.
A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.
This commit was automatically created and can be verified using
nix-build https://github.com/infinisil/treewide-nixpkgs-reformat-script/archive/a08b3a4d199c6124ac5b36a889d9099b4383463f.tar.gz \
--argstr baseRev 0128fbb0a5
result/bin/apply-formatting $NIXPKGS_PATH
`/var/cache`, `/var/lib`, and `/var/spool` all have 0755 permissions by
default, so should probably be created as such in this script.
See #357447 for discussion.
(cherry picked from commit 7389d32232)
ShellCheck reports the following:
> SC2174 (warning): When used with -p, -m only applies to the deepest
> directory.
Avoid this warning by splitting `mkdir -m MODE -p DIR` into
`(umask MASK && mkdir -p DIR)`.
(cherry picked from commit bfe7bb410f)
otherwise results in 502 bad gateway errors with some clients (which send a lot of cookies?)
Change-Id: I9aadedb7acde0388f060dbb82ccd8788f41ff0e6
(cherry picked from commit 4d8e8de0d9)
The current default configuration, automatic channel selection with
the HT40- capability, is explicitly disallowed by an assertion in this
module.
This is a result of recent change to default to automatic channel
selection in 1047f0a6bf.
(cherry picked from commit 8a97d662dd)
Some github actions that use `bash` expect interactive features to be available. One such action is the [use-nix-shell](https://github.com/rrbutani/use-nix-shell-action) action. I couldn't find a way to override this even with `cfg.extraPackages`, due to the way the path is ordered.
(cherry picked from commit 8c39875ae3)
FRR intends for non-root users to connect to the VTY sockets if they
are members of the frrvty group, however this is not possible if
non-root/non-frr users cannot access the runtime directory. The
sockets used by the FRR daemons for internal IPC are also created in
the runtime directory, however these are created with appropriately
restrictive permissions to prevent interference.
(cherry picked from commit f014b0d415)
With initial commit I missed the `module-list.nix` file and maintainers
field.
Change-Id: If0af670b11370b3634dd7fb89c9707a8fb51c91e
(cherry picked from commit bc678b2892)
