| 12 Mar 2026 |
 ElvishJerricco | but also (for anyone else in the room), this might be serious enough to just go straight to master | 23:30:38 |
| ElvishJerricco | and eat the rebuild of all nixos tests | 23:30:45 |
|  THAMIZHAMUDHU GOPALAN joined the room. | 23:43:19 |
 whispers [& it/fae] | (fwiw staging-nixos merge PR was opened just now by zowoq, though as a draft because of potential kernel regressions: https://github.com/NixOS/nixpkgs/pull/499398) | 23:53:50 |
| whispers [& it/fae] | * (fwiw staging-nixos merge PR was opened an hour ago by zowoq, though as a draft because of potential kernel regressions: https://github.com/NixOS/nixpkgs/pull/499398) | 23:54:04 |
| whispers [& it/fae] | * (note: staging-nixos merge PR was opened an hour ago by zowoq, though as a draft because of potential kernel regressions: https://github.com/NixOS/nixpkgs/pull/499398) | 23:54:25 |
| 13 Mar 2026 |
|  JamieMagee joined the room. | 03:38:10 |
 vcunat | Generally I'm trying to remember to merge also staging-nixos whenever merging staging-next, as almost no tests get pre-cached during staging-next. | 04:59:05 |
| ElvishJerricco | yea that makes sense | 04:59:55 |
 Alyssa Ross | if you're doing that you might as well merge into staging-nixos, then staging-nixos to master, so other pending changes come along | 06:27:41 |
 K900 | staging-nixos is currently held back due to something something regression in stable kernels | 06:28:11 |
| K900 | I am not sure of the details, zowoq is | 06:28:28 |
| Alyssa Ross | surely we should just revert that then? | 06:28:46 |
| K900 | It didn't get merged to master yet | 06:28:56 |
| Alyssa Ross | on staging-nixos | 06:29:24 |
| Alyssa Ross | to avoid exactly this situation | 06:29:35 |
| K900 | Possibly | 06:29:40 |
|  tom joined the room. | 07:28:33 |
| Alyssa Ross | Merged into staging-nixos, and staging-nixos merge queued. | 08:20:21 |
| ElvishJerricco | cool, thank you | 08:21:27 |
| K900 | Probably want to also bonk the staging-next automerge | 08:26:09 |
 Arian | Should we create a NixOS-specific advisory for this one? Given we're one of the few Distros in the bucket "new systemd version + machined by default" | 09:25:13 |
 emily | maybe just post on the Discourse security announcements forum | 09:46:14 |
| Arian | Lmao redhat filed a CVE for it | 14:48:56 |
| Arian | https://www.cve.org/CVERecord?id=CVE-2026-4105 | 14:49:11 |
| Arian | And the CVE is wrong. Marks more things as affected than needed. Great. | 14:49:40 |
 magic_rb | you mean that rhel7 is not affected? | 14:53:34 |
| K900 | New kernels with apparmor security fixes: https://lore.kernel.org/stable/2026031357-statistic-surrogate-41a7@gregkh/T/#t | 16:46:35 |
| K900 | Someone please do the dance | 16:46:45 |
 ma27 | ok, on it. | 16:56:43 |
