!UNVBThoJtlIiVwiDjU:nixos.org

Staging

393 Members
Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen128 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
13 Mar 2026
@vcunat:matrix.orgVladimír ČunátThere's still x86_64-darwin openblas06:36:57
@vcunat:matrix.orgVladimír Čunát It's time for some staging-nixos, as discussed in #security:nixos.org 06:38:30
@k900:0upti.meK900Then I guess we have to revert the kernel bump06:41:13
@vcunat:matrix.orgVladimír ČunátDarwin builds tend to get stuck now on "sending inputs". (no idea why or what's changed) Maybe that's making things worse.06:47:32
@qyliss:fairydust.spaceAlyssa RossUnclear to me what's going on with the kernels because nobody posted what the regression actually is07:49:23
@vcunat:matrix.orgVladimír ČunátSimply unblocking the other changes sounds reasonable to me.07:57:19
@qyliss:fairydust.spaceAlyssa RossYeah, I guess. Just a shame to revert the kernels when there could be no significant issue with them.07:57:57
@qyliss:fairydust.spaceAlyssa RossOkay the kernels are confirmed fine.08:09:44
@rvdp:infosec.exchangeRamses 🇵🇸is there any docs on how to fix a merge conflict when merging master in -next? I don't immediately find anything by grepping in the repo. Is this just manual merge and push?11:29:41
@rvdp:infosec.exchangeRamses 🇵🇸* are there any docs on how to fix a merge conflict when merging master into -next? I don't immediately find anything by grepping in the repo. Is this just manual merge and push?11:30:03
@k900:0upti.meK900 Yes 11:31:08
@rvdp:infosec.exchangeRamses 🇵🇸ok, fix is trivial (go version difference), I'll push the merge then11:34:21

Show newer messages


Back to Room ListRoom Version: 6