| 23 Feb 2026 |
 Vladimír Čunát | (you're certainly welcome to continue directly on master) | 12:15:44 |
 K900 | Are we doing 25.11 after or another master | 12:48:59 |
| K900 | 5dc0d4be0086 nss: 3.112.2 -> 3.112.3 [github-actions[bot]]
903014c709a7 perlPackages.CryptURandom: 0.54 -> 0.55 [github-actions[bot]]
23869dd3f201 zlib: 1.3.1 -> 1.3.2 [github-actions[bot]]
d8c60a87c9fe libvpx: 1.15.2 -> 1.16.0 [Martin Weinelt]
529cd1c52d0c capstone: 5.0.6 -> 5.0.7 [Robert Scott]
d251f26173fc unzip: vendor CVE-2021-2417.patch [github-actions[bot]]
0316de609448 mimir: 3.0.2 -> 3.0.3 [Adam C. Stephens]
2734a39cd5e4 mimir: 3.0.1 -> 3.0.2 [Adam C. Stephens]
6366e2d52182 libpq: 18.1 -> 18.2 [github-actions[bot]]
e401c4e928db libsoup_3: add patch for CVE-2025-11021 [github-actions[bot]]
48b03458adf7 python3Packages.pillow: 12.1.0 -> 12.1.1 [github-actions[bot]]
749fb38d44df modemmanager: 1.24.0 -> 1.24.2 [github-actions[bot]]
c6a7862853cc python3Packages.cryptography: 46.0.4 -> 46.0.5 [Martin Weinelt]
eb03b7e39bcb python3Packages.cryptography: 46.0.3 -> 46.0.4 [Martin Weinelt]
308ba5020bc7 python3Packages.cryptography: 46.0.2 -> 46.0.3 [Martin Weinelt]
127574d8aead phpPackages.imagick: cleanup [asrar]
a2d2740a4302 imagemagick: fix cross compile [asrar]
8096ec799765 phpPackages.imagick: fix cross compilation [asrar]
12a9f5b9509f libpng: 1.6.54 -> 1.6.55 on darwin [Vladimír Čunát]
fd1b3906df94 libpng: 1.6.54 -> 1.6.55 on non-darwin [Vladimír Čunát]
1688efe84ad6 linux/common-config: enable DSI output for RK3588 SoCs [github-actions[bot]]
2f37758ae23b python313: 3.13.11 -> 3.13.12 [github-actions[bot]]
58208015467b python314: 3.14.2 -> 3.14.3 [github-actions[bot]]
d7b09311a9f1 go_1_25: 1.25.6 -> 1.25.7 [github-actions[bot]]
4ec7bd6831cd linux/common-config: disable nova_core and drm_nova [Gary Guo]
5b1b7b30e951 linux/common-config: remove obsolete hack [Gary Guo]
fbbd5ee387c9 libsoup_3: soup-init: Use libdl instead of gmodule in soup2_is_loaded [github-actions[bot]]
1fac75104084 expat: 2.7.3 -> 2.7.4 [github-actions[bot]]
fabf792f20f9 cryptsetup: 2.8.3 -> 2.8.4 [github-actions[bot]]
6d27dfd022a2 publicsuffix-list: 0-unstable-2025-12-28 -> 0-unstable-2026-01-25 [github-actions[bot]]
2dd9fa9c642a lowdown: 2.0.3 -> 2.0.4 [github-actions[bot]]
83146924c714 lowdown: 2.0.2 -> 2.0.3 [github-actions[bot]]
972dc0985b01 lowdown: add unsandboxed variant to passthru.tests [github-actions[bot]]
88eb4509f919 lowdown: unset doInstallCheck instead of emptying installCheckPhase [github-actions[bot]]
| 12:49:59 |
| K900 | There's really not a lot on 25.11 | 12:50:04 |
| Vladimír Čunát | A few more are open:
https://github.com/NixOS/nixpkgs/pulls?q=base%3Astaging-25.11+is%3Aopen | 12:51:59 |
| Vladimír Čunát | (including some security fixes) | 12:52:10 |
| 24 Feb 2026 |
| Vladimír Čunát | Uh, I forgot to add staging-nixos before that. Way too late now; we already have all tests built and nixos-unstable is activating. | 04:55:52 |
| Vladimír Čunát |
There's really not a lot on 25.11
Added 5 more lines.
| 07:17:55 |
| Vladimír Čunát | I think 25.11, as (up to) one month delay is long enough for security fixes as it is. | 07:18:34 |
| Vladimír Čunát | * I think 25.11, as (up to) one month delay is long enough for security fixes already. | 07:18:51 |
| Vladimír Čunát | New staging-next-25.11:
https://github.com/NixOS/nixpkgs/pull/493587 | 07:31:06 |
| Vladimír Čunát | The first change in there was merged on Jan 25, so the delay will be more like 5 weeks. | 07:31:34 |
| Vladimír Čunát | (though the first real security fix was merged about a week later) | 07:32:50 |
| Vladimír Čunát | Redacted or Malformed Event | 07:45:13 |
 Alyssa Ross | Wonder if that's automatable. Feels like it should be... | 07:45:47 |
| K900 | We can probably auto-merge staging-nixos into next? | 07:46:26 |
| K900 | Like instead of going master -> next -> staging, we can go master -> staging-nixos -> next -> staging | 07:46:42 |
|  makefu joined the room. | 13:02:48 |
| Alyssa Ross | Oh yeah perfect | 14:48:50 |
 tazjin | we're several versions behind on libxkbcommon (~ every GUI thing depends on it), I rebuilt the world and tested with this PR: https://github.com/NixOS/nixpkgs/pull/487689
no build failures across a bunch of heterogeneous nixos configs with lots of desktop software, and the systems I've tested run fine. I think it makes sense to move forward with this, as it's going to start blocking more and more updates (right now, for example, latest river depends on tihs)
| 14:57:30 |
| K900 | Sure, let's just get this in | 14:59:20 |
| makefu | hey all, currently calibre is broken on unstable and master ( https://hydra.nixos.org/build/322102655 ), last success was at https://hydra.nixos.org/build/321911294 . error message states it cannot find qt6 qmake anymore. i tried to pinpoint the issue (or have rather have mr computer trying to build the package until it is successful) and it came up with the following solution https://p.krebsco.de/1x23192 however i have absolutely no idea if this is a good idea and i had no plan to touch qt6 buildhooks in first place.
setting env.QMAKE="${qt6.qtbase}/bin/qmake" in calibre directly didnt help
before i create a PR, could anybody have a quick look at the solution above?
| 17:37:25 |
| K900 | I believe we have a fix for that in the next staging | 17:37:43 |
| makefu | is staging-next more "fresh" than master? | 17:38:26 |
| K900 | No | 17:39:36 |
| K900 | staging-next is currently behind master, as Hydra is building staging-25.11 | 17:39:45 |
| K900 | We should have the next staging-next cycle probably somewhere around the end of the week | 17:40:02 |
| makefu | the issue still exists in master when trying to build calibre | 17:52:33 |
| K900 | Yes, and the fix is in staging | 17:52:51 |
| K900 | Not staging-next | 17:52:52 |
