feat(nas): channel → nixos-26.05 #117
No reviewers
Labels
No labels
bug
enhancement
in-progress
needs-info
needs-triage
p0
ready-for-agent
ready-for-human
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Cloonar/nixos!117
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "afk/103"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bumps
hosts/nas/channelto nixos-26.05 (staged fleet upgrade 2/6, after nb).26.05 removed three things nas depends on, so the bump is more than a one-line channel change. Each removal is handled nas-locally so no other host is touched:
pyload-ngpackage and theservices.pyloadmodule (CVEs + unmaintained upstream). Re-provided nas-locally:pkgs/pyload-ng(rebuilds the 25.11 derivation directly — pinned commit, declarative-env patch, relaxed bounds) plus its orphaned depsdukpyandflask-themes2, wired throughoverlays/pyload-ng.nix. The removed module is vendored asmodules/pyload-service.nixunder the option pathservices.pyloadVendored(26.05 forbids redefining the removedservices.pyload). The generated unit/user/group are still namedpyload, somodules/pyload.nixoverrides apply unchanged. CVEs consciously accepted — LAN-only — and gated viaallowInsecurePredicate.permittedInsecurePackages→allowInsecurePredicate. Consolidates both insecure allowances: the vendoredpyload-ng, andpypy2.7-*(26.05'smakePythonWriterinterpreter guard force-evaluates the pypy2 set during any Rust package'sfetch-cargo-vendor-util; the insecure members never enter the closure).services.promtail(Promtail is EOL). ⚠️ This pauses central journald→Loki shipping on nas (local journald is intact). See note below — this is a fleet-wide concern, not nas-specific.Kernel pin (
linuxPackages_6_18) self-collapses on 26.05 as designed (default kernel is already 6.18).stateVersionunchanged (24.05).Verification
Full
nix-build '<nixpkgs/nixos>' -A systemagainst nixos-26.05 — green:nixos-system-nas-26.05.1183.6b316287bae2pyload-ng,dukpy,flask-themes2build and land in the closure (unit-pyload.servicerealized)udevadm verify(eval alone would not catch this)Closes #103. Reboot/verify onto 26.05 is the human follow-up in #104.
⚠️ Fleet-wide follow-up: promtail removal
utils/modules/promtailis shared by amzebs-01, fw, mail, nas, web-arm. nas is the first to 26.05, so it drops the import here, but every remaining host bump (#105–#112) hits the same removal. There is currently no tracking issue for migrating central logging to grafana-alloy (or formally retiring it). Worth filing before the next host bump so logging isn't silently lost fleet-wide.Filed the promtail→alloy migration as #118 (the fleet-wide follow-up noted above). Per its sequencing, it should land before fw (#105) is armed so the remaining 26.05 bumps don't silently lose central logging.