summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorFlorian Klink <flokli@flokli.de>2020-01-21 14:21:57 +0100
committerzimbatm <zimbatm@zimbatm.com>2020-01-21 13:21:57 +0000
commit0daae2e08c1b5c0d4141f6655d38bac7b70569e7 (patch)
treefdab1abb43cc201313ca0b4d28f8091c54e50d7d /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parentab10bac1b177832b5e6b883ba95bf35f87229267 (diff)
nixos/buildkite: drop user option (#78160)
* nixos/buildkite: drop user option This reverts 8c6b1c3eaaa8b555bddaced3ab6f02695bef1541. Turns out, buildkite-agent has logic to write .ssh/known_hosts files and only really works when $HOME and the user homedir are in sync. On top of that, we provision ssh keys in /var/lib/buildkite-agent, which doesn't work if that other users' homedir points elsewhere (we can cheat by setting $HOME, but then getent and $HOME provide conflicting results). So after all, it's better to only run the system-wide buildkite agent as the "buildkite-agent" user only - if one wants to run buildkite as different users, systemd user services might be a better fit. * nixosTests.buildkite-agent: add node with separate user and no ssh key
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions