-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nixos/wg-access-server: bugfix missing cfg dns.enabled #352839
Conversation
@@ -104,7 +104,7 @@ in | |||
let | |||
capabilities = [ | |||
"CAP_NET_ADMIN" | |||
] ++ lib.optional cfg.settings.dns.enabled "CAP_NET_BIND_SERVICE"; | |||
] ++ lib.optional cfg.settings.dns.enable "CAP_NET_BIND_SERVICE"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is true that this is a typo, but the typo isn't here it's in line 21. As the settings.* options are RFC 42 style options, we mirror upstream config options. See https://www.freie-netze.org/wg-access-server/2-configuration/#:~:text=dns.enabled
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pure technically, the RFC42 compliance is right here.
But this will make a lot of people trip. PR updated.
d06f2fa
to
a58c8fe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The enabled Option
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Also mkRenamedOptionModule doesn't really make sense as it was broken before.
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release-24.05
git worktree add -d .worktree/backport-352839-to-release-24.05 origin/release-24.05
cd .worktree/backport-352839-to-release-24.05
git switch --create backport-352839-to-release-24.05
git cherry-pick -x a58c8fee1e265904132803d4d4d8c1d9c56dee71 |
Successfully created backport PR for |
Well of course we can backport this to 21.11, do to wg-access-server simply not being in that release ^^ |
Seems to me a plain and simple typo.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.