| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
nixos/plasma5: Dont add samba a second time to `environment.systemPackages`
|
|
nixos/winbox: init
|
|
This fixes a panic of the kubo daemon which could occur under certain conditions when the daemon was starting.
It was caused by the `ipfs.service` unit not depending on the `ipfs-api.socket` and `ipfs-gateway.socket` units with `Wants=`. This allows the `ipfs.service` to be started manually or by `nixos-rebuild` without the sockets being set up before that. When that happens, the daemon won't know about these sockets and will only use what is set in `services.kubo.settings.Addresses.Gateway` and `services.kubo.settings.Addresses.API`. By default the `API` is an empty list in NixOS though. The daemon doesn't like this at all and panics on startup, see https://github.com/ipfs/kubo/issues/10056.
With this commit, starting `ipfs.service` will first set up the two sockets before starting the actual service.
Adding the `Sockets=` option implicitly adds a `Wants=` for the sockets and this is exactly what we need. See https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html#Implicit%20Dependencies . This can be checked with `systemctl show ipfs.service`.
This should probably be upstreamed to the unit file in the Kubo repo.
The problem can be reproduced in the following way:
- Add `services.kubo.enable = true` to `/etc/nixos/configuration.nix`
- `sudo nixos-rebuild switch` (this may already fail, not sure why it's not deterministic for me)
- `sudo systemctl stop ipfs-api.socket`
- `sudo systemctl stop ipfs-gateway.socket`
- `sudo systemctl stop ipfs.service`
- `sudo systemctl start ipfs.service`
Fixes #248447.
|
|
kubo: 0.24.0 -> 0.25.0
|
|
nixos/quicktun: clean up module, add tests
|
|
|
|
drbd: fix path to drbdadm
|
|
nixos/udev: allow /bin/sh in udev rules
|
|
Unblock channels
|
|
zammad: 6.1.0 -> 6.2.0
|
|
Unbreaks installer tests that otherwise start depending on i686-glibc
|
|
|
|
hardened kernel: test 6.6 & remove obsolete 4.14 from patches.json
|
|
nextcloud28: init at 28.0.0, nextcloud27: 27.1.4 -> 27.1.5, nextcloud26: 26.0.9 -> 26.0.10
|
|
nixos/{sysctl,caddy}: improvements for net.core.wmem_max
|
|
this patch adjusts the `boot.kernel.sysctl."net.core.wmem_max"` to match the
value suggested in the quic-go wiki, just as `"net.core.wmem_max"`.
see fdfdc5df21d3df985b751bc61929e2305882dd48
see https://github.com/quic-go/quic-go/issues/3923
|
|
we previously defined a custom type for `boot.kernel.sysctl."net.core.rmem_max"`
to resolve to the highest value set. this patch adds the same behavior to
`"net.core.wmem_max"`.
as this changes the type from a string to an integer, which is a breaking
change this patch also includes a release note and updates the transmission
module to use a number for `wmem_max`.
|
|
nixos/node-red: fix `cfg.package` default value
|
|
nixos/postgresql: point doc link to current like all others
|
|
Add a new test to check that accessing the Gateway socket also starts the daemon via socket activation.
|
|
The FUSE functionality is completely broken in Kubo v0.24.0.
See https://github.com/ipfs/kubo/issues/10242.
|
|
This fixes the following eval error:
```
error: nodePackages.node-red cannot be found in pkgs
```
when having `services.node-red.enable = true;` without specifying
`services.node-red.package`, just like the nixos VM test.
Follow-up of f509382c11ed445b52f249efa6e2fe66d1b56fa7, which attempted
to fix this as well.
Breakage introduced in 0a37316d6cfea44280f4470b6867a711a24606bd.
|
|
props: @cody4k for the fix
Fixes #268172
|
|
nixos/doc: include section for 24.05
|
|
|
|
People are actively writing release notes already and with this it's
ensured that the contents are actually valid.
Also, when writing release notes for something, I'd like to be able to
see a preview.
|
|
Using `/bin/sh` in udev rules is fine (as it's guaranteed to point to a
(bash) shell on NixOS), and actually is better than hardcoding absolute
paths, at least in cases where these rules are also added to the
(systemd-based) initrd (via boot.initrd.services.udev.rules).
To allow this, we need to update the check routine that assembles the
list of files needing fixup, to explicitly exclude `/bin/sh` occurences.
To do this, we convert the pattern to a PCRE regex (which requires "/"
to be escaped), and add `(?!/bin/sh\b)` as a negative lookahead.
This subsequently allows udev rules to (start using) `/bin/sh` again, so
they'll work in-initrd.
|
|
It seems like Zammad and the postgreSQL need more then 1 GB memory after
the update to Zammad 6.2.0. So this commit sets the memory limit to 2 GB.
|
|
|
|
* Always use PHP 8.2: at the time of writing, Nextcloud also suggests to
use 8.2 rather than 8.3 in the manual for v28.
One contributing factor is probably that all plugins need new releases
to declare PHP 8.3 support.
* Fix upgradeWarning for installing v27 now that v28 is out.
* Drop upgrade warning for v24. This one is EOL for quite a while
already, so right now everybody should've switched (or carefully
studied the release notes in case they were upgrading from <23.05) and
we can clean up the module a little bit.
v25 was dropped not so long ago, so if it's still referenced (because
somebody didn't declare `services.nextcloud.package` and has
`system.stateVersion = "22.11";`) it's appropriate to still give a
specialized error.
|
|
nixos/udev: update defaultText for services.udev.path
|
|
services.udev.path already contains some defaults, these are however
defined in the module implementation, not options.
Update the description to make this more clear.
|
|
treewide: replace references to matrix-org/synapse with element-hq/synapse
|
|
nixos/wpa_supplicant: Ensure the generated config isn't world-readable
|
|
nixos/snapraid: remove from top-level
|
|
ceph: use absolute binary paths instead of relative paths
|
|
nixos/river: add xdg.portal.config
|
|
nixos/vdirsyncer: fix config.statusPath option
|
|
nixos/jigasi: update to use literalExpression
|
|
QMK's udev rules are setting hidraw devices's group to plugdev.
|
|
nixos/lib/test-driver: make wait_for_unit ask for ActiveState only
|
|
If we include users with unset groups, we get this very confusing
message, with invalid Nix code:
- The following users have a primary group that is undefined: qyliss
Hint: Add this to your NixOS configuration:
users.groups. = {};
We don't need to include such users in this check, since they'll be
caught anyway by this one:
- users.users.qyliss.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.qyliss.group = "qyliss";
users.groups.qyliss = {};
|
|
|
|
|
|
element-hq/synapse
|
|
|
|
nixos/restic: append PATH in wrappers instead of overwriting
|
|
nixos/stub-ld: init module
|
|
nixos/prometheus: add remote{Read, Write}.headers options
|
|
Hyprland now works on Nvidia without patching.
|
