!UNVBThoJtlIiVwiDjU:nixos.org

Staging

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

Load older messages


SenderMessageTime
8 Jul 2025
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)but i won't be opening that PR today, so if anyone wants so replace some gits in the early stack then feel free to use these ^^21:42:09
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)sleep is preferred.21:42:19
@vcunat:matrix.orgVladimír ČunátThat won't help us now, right? Just next time.21:42:30
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)yea21:42:36
@fabianhjr:matrix.orgFabián Heredia Regarding now, I think the best option is what Alyssa Ross proposed (merging staging-next to the main branch and starting a new staging-next cycle with git 2.50.1) 22:16:47
@fabianhjr:matrix.orgFabián HerediaWell, regardless, merging into staging meanwhile, regardless if this cycle is scrapped (vcunant mentioned pulling the rest of staging) or a new one is started this would pulled from staging.22:23:27
@sandro:supersandro.deSandroGreat idea! Did something similar with openssh a while ago.22:32:36
@dgrig:erethon.comdgrig joined the room.22:36:56
@fabianhjr:matrix.orgFabián Heredia* Well, merging into staging meanwhile, regardless if this cycle is scrapped (vcunant mentioned pulling the rest of staging) or a new one is started this would pulled from staging.22:39:51
9 Jul 2025
@yuka:yuka.devYureka (she/her)

redis/valkey tests are so flaky again

*** [err]: replica buffer don't induce eviction in tests/unit/maxmemory.tcl
00:34:13
@yuka:yuka.devYureka (she/her)I tried on 3 different x86 hosts00:34:24
@yuka:yuka.devYureka (she/her)(otherwise everything on staging-next + git update works for my server)00:35:19
@charles:hax0rbana.orgch joined the room.02:48:29
@vcunat:matrix.orgVladimír Čunát Or alternatively, staging-next-25.05 might go first, as it has older security fixes as well. 05:07:03
@alina:catgirl.cloudalina arielle amelie🏳️‍⚧️🐾are people here already aware of this https://blog.fyralabs.com/btrfs-corruption-issues/09:05:01
@vcunat:matrix.orgVladimír ČunátThat just requires regular kernel update, right?09:06:44
@vcunat:matrix.orgVladimír Čunát* That just requires a normal kernel update, right?09:06:54
@k900:0upti.meK900Yes09:07:00
@k900:0upti.meK900We should be 6.15.5 everywhere now09:07:05
@yuka:yuka.devYureka (she/her)So no relevancy for staging09:07:11
@alina:catgirl.cloudalina arielle amelie🏳️‍⚧️🐾ah i see, good09:07:20
@vcunat:matrix.orgVladimír Čunát "everywhere": well, the nixos-unstable channel is still on 6.15.4. 09:09:01
@vcunat:matrix.orgVladimír Čunát And nixos-25.05 as well. 09:09:15
@vcunat:matrix.orgVladimír Čunát25.05 should be a matter of just a few minutes (incidentally), -unstable hopefully today.09:10:57
@vcunat:matrix.orgVladimír ČunátJust regular lagging.09:11:00
@vcunat:matrix.orgVladimír Čunát * 25.05 should be a matter of just a few minutes (incidentally), -unstable hopefully today (tested job succeeded already). 09:11:19
@alina:catgirl.cloudalina arielle amelie🏳️‍⚧️🐾so would it be too late to add a warning or smth that prevents users from upgrading to that version without being aware of this regression?09:11:33
@k900:0upti.meK900Yes09:11:53
@k900:0upti.meK900We can't retroactively update channels really09:11:59
@vcunat:matrix.orgVladimír Čunát🤔 it wouldn't be hard technically, I suppose. But we certainly don't have a workflow for that.09:13:13

Show newer messages


Back to Room ListRoom Version: 6