| Age | Commit message (Collapse) | Author |
|---|
|
mart-w/fix/nixos/paperless-ng-fix-164615-consumation-bug
nixos/paperless-ng: fix #164615
|
|
NixOS/auto-upgrade: offer the possibility to define a reboot window during which the system may be automatically rebooted
|
|
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.
|
|
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
|
|
|
|
nixos: systemd: split off helper functions into systemd-lib
|
|
nextcloud21: remove
|
|
|
|
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).
|
|
os-release: preserve fields from being excessively quoted
|
|
pacemaker: init
|
|
|
|
EOLed by upstream in 2022-02[1].
[1] https://docs.nextcloud.com/server/23/admin_manual/release_schedule.html#older-versions
|
|
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.
|
|
(In cases it is unnecessary)
|
|
Remove ancient unfree bitmap fonts from fonts.defaultXFonts
|
|
|
|
|
|
plantuml-server 1.2021.12 -> 1.2022.2
|
|
nixos/mate: allow remove any added package
|
|
nixos/switch-to-configuration: fix installBootLoader escaping
|
|
prometheus-dmarc-exporter: init at 0.5.1
|
|
nixos/pantheon: enable xdg desktop integration
|
|
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.
|
|
See https://github.com/NixOS/nixpkgs/issues/160740
|
|
nixos/tomcat: configure default group and fix broken default package …
|
|
to be accessed
|
|
nixos/switch-to-configuration: Few minor/medium improvements
|
|
sdboot-builder: fix crash in exception handling
|
|
|
|
|
|
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 = {};
|
|
|
|
Also some cleanups.
|
|
|
|
This prevents the embarrassing situation in https://github.com/NixOS/nixpkgs/pull/163828 from happening again.
|
|
pomerium: 0.15.7 -> 0.17.0
|
|
epgstation: 1.7.5 -> 2.6.20
|
|
|
|
As a novice to using this module, I found the existing description to be
quite misleading. It does not at all disable pulling from the registry,
it just loads some image archive that may or may not be related to the
container you're specifying. I had thought there was extra magic behind
this option, but it's just a `docker load`. You need foreknowledge of
the contents of the archive so that whatever it contained is actually
used to run the container.
I've reworded the description to hopefully make this behavior clearer.
|
|
|
|
|
|
|
|
|
|
Only extra packages removable currently, but it's possible to run MATE without packages like caja or yelp
|
|
|
|
|
|
This bug is so obscure and unlikely that I was honestly not able to
properly write a test for it. What happens is that we are calling
handleModifiedUnit() with $unitsToStart=\%unitsToRestart. We do this to
make sure that the unit is stopped before it's started again which is
not possible by regular means because the stop phase is already done
when calling the activation script.
recordUnit() still gets $startListFile, however which is the wrong file.
The bug would be triggered if an activation script requests a service
restart for a service that has `stopIfChanged = true` and
switch-to-configuration is killed before the restart phase was run. If
the script is run again, but the activation script is not requesting
more restarts, the unit would be started instead of restarted.
|
