!UNVBThoJtlIiVwiDjU:nixos.org

Staging

383 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 | Review Reports: https://malob.github.io/nix-review-tools-reports/124 Servers

Load older messages


SenderMessageTime
14 Jun 2026
@k900:0upti.meK900 Doesn't seem like it 20:54:26
@k900:0upti.meK900 There hasn't been an -rc1 even 20:56:01
@hexa:lossy.networkhexaso waiting until next friday seems weird21:14:23
@k900:0upti.meK900Feel free to do the merge then21:20:06
@k900:0upti.meK900 I'm going to bed 21:20:11
@zowoq:matrix.orgzowoqhttps://github.com/NixOS/nixpkgs/pull/53180822:57:59
@kuflierl:matrix.orgkuflierlCould we fast track https://github.com/NixOS/nixpkgs/pull/522835 and https://github.com/NixOS/nixpkgs/pull/527164? libheif had a lot of critical CVEs and the pr is already 3 weeks old. 23:39:45
15 Jun 2026
@whispers:catgirl.cloudwhispers [& it/fae]it's in the current staging-next-26.05 which is the best you can do00:02:42
@whispers:catgirl.cloudwhispers [& it/fae] * 00:03:00
@whispers:catgirl.cloudwhispers [& it/fae] * 00:03:15
@whispers:catgirl.cloudwhispers [& it/fae] * it's in the current staging-next-26.05 and will be in the upcoming staging-next, which is the best you can do. unfortunate reality of staging. 00:06:18
@hexa:lossy.networkhexauntil the new queue runner fixes throughput 🤞00:16:03
@hexa:lossy.networkhexacould happen any day now00:16:20
@kuflierl:matrix.orgkuflierlI really should have just merged it into main using the security bypass exception01:02:09
@kuflierl:matrix.orgkuflierl* I really should have just merged it into master using the security bypass exception01:02:22
@kuflierl:matrix.orgkuflierlAlso, I just noticed that the github link in the channel description still points to 25.1101:19:21
@kuflierl:matrix.orgkuflierl* Also, I just noticed that the github link in the channel description still points to 25.11. should probably be updated01:19:35
@vcunat:matrix.orgvcunat Oh, so we should delay the thoughts on dropping most nixos.tests.* from the jobsets? 06:28:43
@vcunat:matrix.orgvcunat * Oh, so we should delay the thoughts on dropping most nixos.tests.* from the jobsets after we try with the new queue runner? 06:28:56
@vcunat:matrix.orgvcunat We're getting thousands of home-assistant rebuilds on nixpkgs master on daily basis now:
https://hydra.nixos.org/job/nixpkgs/unstable/home-assistant.x86_64-linux
06:36:42
@vcunat:matrix.orgvcunatThat blocked eval, I believe: https://github.com/NixOS/nixpkgs/pull/53190907:47:31
@vcunat:matrix.orgvcunatWe do ship the latest kernel in the ISO.07:48:00
@k900:0upti.meK900Ughhhhhhhh07:48:04
@k900:0upti.meK900Yeah probably07:48:07
@k900:0upti.meK900We might want to demote bcachefs to LTS kernels only tbh07:48:30
@k900:0upti.meK900Like we already do with zfs07:48:31
@elvishjerricco:matrix.orgElvishJerricco We already removed the kernelPackages setting from the module since we know it'll be fine on LTS going forward. The un-fine-ness was why it wasn't in the LTS specialisation of the ISO originally. So yea it would make sense to give it the ZFS treatment and have it in the LTS specialisation but not the latest kernel one for the ISO 14:08:55
@elvishjerricco:matrix.orgElvishJerricco well, other than the fact that kent has said he intends to have bcachefs releases for new kernels before new kernels release, so it should be fine on the latest kernel specialisation as long as nixpkgs updates bcachefs before the kernel 14:10:34
@hexa:lossy.networkhexaMost of these are version bumps of home-assistant itself, that cause package tests to be rebuilt. I hope new queue-runner will cause some relief here.17:00:49
@grimmauld:m.grimmauld.deGrimmauld (any/all)Also: All the failing jobs we have, those are rebuilt each time hydra loops over, right? So marking more shit as broken means less load on hydra? Or am i misunderstanding something?17:02:30

Show newer messages


Back to Room ListRoom Version: 6