| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| |
| |
| | |
mart-w/fix/nixos/paperless-ng-fix-164615-consumation-bug
nixos/paperless-ng: fix #164615
|
| | |
| |
| |
| |
| |
| | |
Add an exception to the `paperless-ng-server` service's
`SystemCallFilter` as the `mbind` syscall is needed when consuming a
document while having a classification model present.
|
| |\ \
| |/
|/| |
NixOS/auto-upgrade: offer the possibility to define a reboot window during which the system may be automatically rebooted
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
which the system may be automatically rebooted
Some systems should not be rebooted at just any time. If the upgrade process takes too long, for instance because of a
slow internet connection, or if the upgrade service is ran during production hours, we want to allow to define a window
outside of which a reboot will not be performed.
The system will then reboot on the next run of the upgrade service which finishes inside the reboot window.
E.g. we can run the update service twice per week, once during the night and once during the day, but reboots are only
allowed during the night. By doing so, a system that is usually shut down during the night will still receive updates
and systems that are turned on 24/7 can be rebooted outside of production hours.
Co-authored-by: Silvan Mosberger <github@infinisil.com>
|
| | |
| |
| |
| | |
This reverts commit 1c58cdbeed880e99d816c234a954d4cdfc073b6c, since this change was made redundant by 3dc6fab5c9362db2cf079ffa15f2b62b05001747 and in https://github.com/NixOS/nixpkgs/pull/145013 we decided to revert this commit.
|
| |\ \
| | |
| | | |
Throw an error for options without a type
|
| | | |
| | |
| | |
| | | |
Co-Authored-By: Janne Heß <janne@hess.ooo>
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It doesn't make sense to have a default value for this that's
incompatible with the default locate implementation. It means that
just doing services.locate.enable = true; generates a warning, even if
you don't care about pruning anything. So only use the default prune
list if the locate implementation supports it (i.e., isn't findutils).
|
| |\ \ \ \
| | | | |
| | | | | |
nixos: systemd: split off helper functions into systemd-lib
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
nextcloud21: remove
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
EOLed by upstream in 2022-02[1].
[1] https://docs.nextcloud.com/server/23/admin_manual/release_schedule.html#older-versions
|
| |\ \ \ \ \ \ |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
os-release: preserve fields from being excessively quoted
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
(In cases it is unnecessary)
|
| |\ \ \ \ \ \ \ \
| |_|_|_|/ / / /
|/| | | | | | | |
pacemaker: init
|
| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \
| |_|_|_|/ / / /
|/| | | | | | | |
ibus: 1.5.24 -> 1.5.26
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
When `services.resolved.enable` is set to true, the file /etc/resolv.conf becomes a symlink to /etc/static/resolv.conf, which is a symlink to /run/systemd/resolve/stub-resolv.conf. Without this commit, tor does not have access to this file thanks to systemd confinement. This results in the following warning when tor starts:
```
[warn] Unable to stat resolver configuration in '/etc/resolv.conf': No such file or directory
[warn] Could not read your DNS config from '/etc/resolv.conf' - please investigate your DNS configuration. This is possibly a problem. Meanwhile, falling back to local DNS at 127.0.0.1.
```
To fix this, simply allow read-only access to the file when resolved is in use.
According to https://github.com/NixOS/nixpkgs/pull/161818#discussion_r824820462, the symlink may also point to /run/systemd/resolve/resolv.conf, so allow that as well.
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Remove ancient unfree bitmap fonts from fonts.defaultXFonts
|
| | |/ / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | | |
See https://github.com/NixOS/nixpkgs/issues/160740
|
| | |_|_|_|/ / /
|/| | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
plantuml-server 1.2021.12 -> 1.2022.2
|
| | | |_|_|/ / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
- changed JDK version to 17 (11+ required)
- added maven build reproducibility
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
nixos/mate: allow remove any added package
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Only extra packages removable currently, but it's possible to run MATE without packages like caja or yelp
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
nixos/switch-to-configuration: fix installBootLoader escaping
|
| | | |_|/ / / / /
| |/| | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Use a quoted heredoc to inject installBootLoader safely into the script,
and restore the previous invocation of `system` with a single argument so
that shell commands keep working.
|
| |\ \ \ \ \ \ \ \
| |_|_|_|_|/ / /
|/| | | | | | | |
prometheus-dmarc-exporter: init at 0.5.1
|
| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \
| |_|/ / / / / /
|/| | | | | | | |
nixos/pantheon: enable xdg desktop integration
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This prevents the embarrassing situation in https://github.com/NixOS/nixpkgs/pull/163828 from happening again.
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
nixos/tomcat: configure default group and fix broken default package …
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Without this fix, evaluating a NixOS configuration with Tomcat enabled and the
default settings results in the following evaluation error:
Failed assertions:
- users.users.tomcat.group is unset. This used to default to
nogroup, but this is unsafe. For example you can create a group
for this user with:
users.users.tomcat.group = "tomcat";
users.groups.tomcat = {};
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
to be accessed
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
nixos/switch-to-configuration: Few minor/medium improvements
|
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|