feat(nas): channel → nixos-26.05 [upgrade 2/6 · bump] #103

New issue

Closed

opened 2026-06-06 12:07:02 +02:00 by dominik.polakovics · 1 comment

dominik.polakovics commented

2026-06-06 12:07:02 +02:00

Owner

▶ Hold until [1/6 · verify] is closed (nb confirmed on 26.05). Then arm: relabel ready-for-agent.

Task: bump hosts/nas/channel to nixos-26.05; open PR.

26.05 specifics for nas:

26.05's default kernel is 6.18, so the boot.kernelPackages = mkIf (versionOlder pkgs.linux.version "6.18.22") linuxPackages_6_18 pin self-disables / collapses to a 6.18 kernel as designed. Confirm it still evaluates (i.e. linuxPackages_6_18 still exists in 26.05). It may be removed later as cleanup — out of scope here.
No ZFS. stateVersion stays 24.05.

Acceptance: PR opens with pre-commit eval green against 26.05.

▶ **Hold** until [1/6 · verify] is closed (nb confirmed on 26.05). Then arm: relabel `ready-for-agent`. **Task:** bump `hosts/nas/channel` to `nixos-26.05`; open PR. **26.05 specifics for nas:** - 26.05's default kernel is 6.18, so the `boot.kernelPackages = mkIf (versionOlder pkgs.linux.version "6.18.22") linuxPackages_6_18` pin **self-disables / collapses to a 6.18 kernel** as designed. Confirm it still evaluates (i.e. `linuxPackages_6_18` still exists in 26.05). It may be removed later as cleanup — out of scope here. - No ZFS. stateVersion stays `24.05`. **Acceptance:** PR opens with pre-commit eval green against 26.05.

dominik.polakovics added the

needs-triage

label

2026-06-06 12:07:02 +02:00

dominik.polakovics referenced this issue

2026-06-07 10:46:16 +02:00

nb: reboot onto 26.05 + verify [upgrade 1/6 · verify] #102

dominik.polakovics commented

2026-06-07 11:13:09 +02:00

Author

Owner

This was generated by AI during triage.

Agent Brief

Category: enhancement (channel upgrade)
Summary: Bump nas to nixos-26.05 — flip the host's channel file and fix only what 26.05 surfaces; leave eval green and a real build clean.

Current behavior:
nas tracks nixos-25.11. Media/NAS host: jellyfin, audiobookshelf, services.pyload (backed by the local utils/pkgs/pyload-ng pin), OpenVPN CyberGhost + custom routing, smartmontools/hdparm disk monitoring, UGREEN LEDs, impermanence, idle auto-shutdown. system.stateVersion = 24.05.

Desired behavior:
nas evaluates and builds cleanly on nixos-26.05 with all services unchanged. Diff = channel flip + minimal required fixes.

Known 26.05 specifics:

boot.kernelPackages pins linuxPackages_6_18 behind versionOlder pkgs.linux.version "6.18.22". Confirm it self-disables (default >= 6.18.22) or still resolves; leave it unless eval forces a change.
services.pyload options must still match; the local pyload-ng pin must still build. Don't broaden its existing CVE acceptance.
pkgs.ugreen-leds-cli, filebot, unrar must still resolve on 26.05.
No allowBroken; the sole udev rule uses a valid %k specifier — udevadm verify (the 26.05 build-gate that bit nb) is not a concern here.

Acceptance criteria:

hosts/nas/channel -> nixos-26.05.
scripts/test-configuration nas eval green on 26.05.
A real system-closure build succeeds — eval-only pre-commit misses 26.05 build-gates (the nb udev-% regression only surfaced post-merge).
Diff limited to the channel flip + required fixes; system.stateVersion stays 24.05.
Any new insecure/unfree allowance justified in the PR (proper fix preferred over blanket masking).

Out of scope:

Removing the now-possibly-redundant linuxPackages_6_18 pin (separate cleanup).
The reboot + runtime verification — that's #104 (ready-for-human).
Touching other hosts' channels.

> *This was generated by AI during triage.* ## Agent Brief **Category:** enhancement (channel upgrade) **Summary:** Bump nas to `nixos-26.05` — flip the host's `channel` file and fix only what 26.05 surfaces; leave eval green and a real build clean. **Current behavior:** nas tracks `nixos-25.11`. Media/NAS host: jellyfin, audiobookshelf, `services.pyload` (backed by the local `utils/pkgs/pyload-ng` pin), OpenVPN CyberGhost + custom routing, smartmontools/hdparm disk monitoring, UGREEN LEDs, impermanence, idle auto-shutdown. `system.stateVersion` = 24.05. **Desired behavior:** nas evaluates and **builds** cleanly on `nixos-26.05` with all services unchanged. Diff = channel flip + minimal required fixes. **Known 26.05 specifics:** - `boot.kernelPackages` pins `linuxPackages_6_18` behind `versionOlder pkgs.linux.version "6.18.22"`. Confirm it self-disables (default >= 6.18.22) or still resolves; leave it unless eval forces a change. - `services.pyload` options must still match; the local pyload-ng pin must still build. Don't broaden its existing CVE acceptance. - `pkgs.ugreen-leds-cli`, `filebot`, `unrar` must still resolve on 26.05. - No `allowBroken`; the sole udev rule uses a valid `%k` specifier — `udevadm verify` (the 26.05 build-gate that bit nb) is not a concern here. **Acceptance criteria:** - [ ] `hosts/nas/channel` -> `nixos-26.05`. - [ ] `scripts/test-configuration nas` eval green on 26.05. - [ ] A real system-closure **build** succeeds — eval-only pre-commit misses 26.05 build-gates (the nb udev-`%` regression only surfaced post-merge). - [ ] Diff limited to the channel flip + required fixes; `system.stateVersion` stays 24.05. - [ ] Any new insecure/unfree allowance justified in the PR (proper fix preferred over blanket masking). **Out of scope:** - Removing the now-possibly-redundant `linuxPackages_6_18` pin (separate cleanup). - The reboot + runtime verification — that's #104 (ready-for-human). - Touching other hosts' channels.

dominik.polakovics added

enhancement

ready-for-agent

and removed

needs-triage

labels

2026-06-07 11:13:09 +02:00

dominik.polakovics referenced this issue from a pull request that will close it,

2026-06-07 12:17:51 +02:00

feat(nas): channel → nixos-26.05 #117

dominik.polakovics referenced this issue

2026-06-07 12:53:04 +02:00