| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
factorio: 1.1.26 -> 1.1.27
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reverted https://github.com/NixOS/nixpkgs/pull/115228 for kodi to avoid conflict.
It does not look like unzip would be used but not investigating now to speed up merge conflict resolution.
|
|
If `openFirewall = true`, but no `firewallFilter` is set, the evaluation
fails with the following error:
The option `services.prometheus.exporters.node.firewallFilter` is defined both null and
not null, in `/home/ma27/Projects/nixpkgs/nixos/modules/services/monitoring/prometheus/exporters.nix'
and `/home/ma27/Projects/nixpkgs/nixos/modules/services/monitoring/prometheus/exporters.nix'.
Originally introduced by me in #115185. The problem is that
`mkOptionDefault` has - as its name suggests - the same priority as the
default-value of the option `firewallFilter` and thus it conflicts if
this declaration and the actual default value are set which is the case
if `firewallFilter` isn't specified somewhere else.
|
|
In the latest release of mautrix-telegram not all secrets can be set
using environment variables (see https://github.com/tulir/mautrix-telegram/issues/584).
This change allows these secret values to be set without ending up in
the Nix store.
|
|
prometheus-jitsi-exporter: init at 0.2.18
|
|
|
|
nixos/miniflux: don't depend on sudo
|
|
nixos/croc: init
|
|
|
|
|
|
|
|
prometheus-systemd-exporter: Init at 0.4.0
|
|
prometheus-knot-exporter: init at 2021-01-30; minor module improvements
|
|
nixos/prometheus-exporters/artifactory: init at 1.9.0
|
|
|
|
nixos/nextcloud: Conditionally enable ImageMagick PHP extension
|
|
The tmpfiles.d rule should only be added if inspectHttps is enabled.
|
|
|
|
apache-kafka: Fix, update and adjust JRE/JVM
|
|
|
|
borgmatic: init at 1.5.12
|
|
When using password_cmd, there's a 'file not found' error due to missing sh binary in path.
For some reason, adding `path = [ "/bin" ]` doesn't fix the issue, but setting `SHELL` does.
Related documentation: https://spotifyd.github.io/spotifyd/config/File.html#shell-used-to-run-commands-indicated-by-password_cmd-or-on_song_changed_hook----omit-in-toc---
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is needed for working external filters, otherwise privoxy will fail
without a clear error message.
|
|
This is a major rewrite of the Privoxy module:
- As per RFC0042, remove privoxy.extraConfig and replace it
with a privoxy.settings option, which maps a NixOS freeform
submodule to the Privoxy configuration format.
- Move all top-level options that mirrored a setting to
the real ones in privoxy.settings. This still keeps the
type-checking, default values and examples in places.
- Add two convenience options: userActions and userFilters, which
simplify the operation of creating a file with pkgs.writeText,
converting it to a string and adding it to the actionsfile/
filterfile list.
- Add a privoxy.inspectHttps option to automagically setup TLS
decryption support. I don't know how long have been waiting
for this feature: can't believe it has just happened.
- Also add a privoxy.certsLifetime to control the periodical
cleanup of the temporary certificates generate by Privoxy.
|
|
nixos/xserver: use modern video drivers
|
|
|
|
... as was suggested in the related issue
|
|
linux: make sure all config options have the same value
|
|
|
|
alerta: move to all-packages.nix and use buildPythonApplication
|
|
|
|
|
|
Anderssorby/acs/fix-minetest-port-option-coercion
nixos/minetest-server: Fix port coercion
|
|
virtualization/amazon-init: enable option
|
|
Currently, kernel config options whose value is "yes" always override
options whose value is "no".
This is not always desired.
Generally speaking, if someone defines an option to have the value
"no", presumably they are disabling the option for a reason, so it's
not always OK to silently enable it due to another, probably unrelated
reason.
For example, a user may want to reduce the kernel attack surface and
therefore may want to disable features that are being enabled in
common-config.nix.
In fact, common-config.nix was already silently enabling options that
were intended to be disabled in hardened/config.nix for security
reasons, such as INET_DIAG.
By eliminating the custom merge function, these config options will
now use the default module option merge functions which make sure
that all options with the highest priority have the same value.
A user that wishes to override an option defined in common-config.nix
can currently use mkForce or mkOverride to do so, e.g.:
BINFMT_MISC = mkForce (option no);
That said, this is not going to be necessary in the future, because
the plan is for kernel config options defined in nixpkgs to use a
lower priority by default, like it currently happens for other module
options.
|
|
nixos/steam: Add port forwarding options
|
|
|
