During patch phase, the path to the fzf binary is overwritten in the vim
plugin source. The sed expression doing this wasn't working because the fzf
code changed in this commit:
https://github.com/junegunn/fzf/commit/02ceae15a235de6b5cd2aca9de070fb3fff78e5b
making the patch useless.
I fixed it and added a check to verify that the plugin was effecively
patched to prevent this to happen in the future.
This is not only to make users aware of the changes but also to give a
heads up to developers which are using the module. Specifically if they
rely on security.dhparams.path only.
Signed-off-by: aszlig <aszlig@nix.build>
This allows to set the default bit size for all the Diffie-Hellman
parameters defined in security.dhparams.params and it's particularly
useful so that we can set it to a very low value in tests (so it doesn't
take ages to generate).
Regardless for the use in testing, this also has an impact in production
systems if the owner wants to set all of them to a different size than
2048, they don't need to set it individually for every params that are
set.
I've added a subtest to the "dhparams" NixOS test to ensure this is
working properly.
Signed-off-by: aszlig <aszlig@nix.build>
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/xterm/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/koi8rxterm -h’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/koi8rxterm help’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/uxterm -h’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/uxterm help’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/xterm -h’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/xterm help’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/.xterm-wrapped -h’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/.xterm-wrapped help’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/.koi8rxterm-wrapped -h’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/.koi8rxterm-wrapped help’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/.uxterm-wrapped -h’ got 0 exit code
- ran ‘/nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333/bin/.uxterm-wrapped help’ got 0 exit code
- found 333 with grep in /nix/store/w5f067zkhadadsz7a2xh1qg435a8cirw-xterm-333
- directory tree listing: https://gist.github.com/1317219946b26e2c85846fe9e169a9e4
When trying to run NSD to serve the root zone, one gets the following
error message:
error: illegal name: '.'
This is because the name of the zone is used as the derivation name for
building the zone file. However, Nix doesn't allow derivation names
starting with a period.
So whenever the zone is "." now, the file name generated is "root"
instead of ".".
I also added an assertion that makes sure the user sets
services.nsd.rootServer, otherwise NSD will fail at runtime because it
prevents serving the root zone without an explicit compile-time option.
Tested this by adding a root zone to the "nsd" NixOS VM test.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @hrdinka, @qknight
Without this change
(coercedTo str toInt int).check "foo"
would evaluate to true, even though
(coercedTo str toInt int).merge {} [{ value = "foo"; }]
will throw an error because "foo" can't be coerced to an int.
We are patching GDM to respect GDM_SESSIONS_DIR environment
variable, which we are setting in the GDM module. Previously, we
only took care of a single code path, the one that handled session
start-up; missing the one obtaining the list of sessions.
This commit patches the second code path, and also whitelists the
GDM_SESSIONS_DIR so that it can be passed to the greeter.
Fixes#34101
Without fcrontab being setuid, every attempt by an user in the fcron
group to edit their own crontab (via `fcrontab -e`) results in the
following error:
```
2018-05-06 11:29:07 ERROR could not change euid to 273: Operation not permitted
2018-05-06 11:29:07 ERROR fcron child aborted: this does not affect the main fcron daemon, but this may prevent a job from being run or an email from being sent.
```
Adding setuid by hand has resolved this issue and aligns with the way
fcrontab is installed on other distributions.
The `haskell-gi` build fails its doctests because of a missing
library; I'm not 100% convinced that setting it to `dontCheck` is the
right thing to do, but I don't have a better idea at the moment.
The `gi-gdkx11` build fails because, surprise, Gdk-X11 isn't found; by
looking around in my store, I found that that that library seems to
live in gtk3 these days; this override is just a stop-gap, though,
I've also submitted the change to cabal2nix that I believe will fix
the automatic generation of the package in the future.
Matías Lang