!UNVBThoJtlIiVwiDjU:nixos.org

Staging

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

Load older messages


SenderMessageTime
2 Nov 2025
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) the PR was opened before staging-next was created and not pushed since, so i just assumed it had no commits that were not already on staging-next and that worked out 23:24:39
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)shit, i botched the musl valgrind, working on it23:31:42
@ivy:faggot.shivyalso sorry guys one of my prs woyld have literally caused every single package to rebuild23:40:37
@winter:catgirl.cloudWinternothing is stopping that from going in staging :-) just not -next23:41:09
@ivy:faggot.shivyno i mean it is in staging-next23:41:44
@winter:catgirl.cloudWinteroh23:41:51
@ivy:faggot.shivy like it was in staging 23:41:57
@ivy:faggot.shivynow its in next23:42:01
@winter:catgirl.cloudWinteri mean this is how staging works23:42:14
@winter:catgirl.cloudWinterso i’m not sure what you’re apologizing about23:42:20
@ivy:faggot.shivyyeah i know but just like its every single package23:42:42
@ivy:faggot.shivybecause of buildEnv23:42:58
@ivy:faggot.shivyone line change smh23:43:29
@ivy:faggot.shivythe outputa dont even change smh its just the hash smh23:43:45
@ivy:faggot.shivy * 23:44:27
@ivy:faggot.shivythere is no remorse for hydra23:44:48
@winter:catgirl.cloudWinterfwiw this would only have been an issue if it got in after -next had already started, probably everything has to rebuild anyways ;^)23:44:59
@winter:catgirl.cloudWinter so no need to apologize 23:45:05
@ivy:faggot.shivy hopefully it everything had to rebuild anyway 23:45:30
@samasaur:matrix.orgsamasaurcan personally confirm that everything downstream of cmake had to, so everything on darwin23:46:08
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)Ugh, now there is ghc eval fails??23:46:27
@winter:catgirl.cloudWintermy favorite23:46:37
@winter:catgirl.cloudWinter:/23:46:38
@ivy:faggot.shivyokay cool so its fine23:48:12
@ivy:faggot.shivywhy is ghc eval failing23:48:28
@samasaur:matrix.orgsamasauri mean as winter said it is the entire point of staging-next, so it would be fine anyway, but yes23:48:42
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)my guess is haskell-updates: https://github.com/NixOS/nixpkgs/pull/45225423:50:48
@vcunat:matrix.orgvcunat We rebuild even stdenv pretty often on staging:
https://hydra.nixos.org/job/nixpkgs/staging/stdenv.x86_64-linux
23:52:37
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)https://github.com/NixOS/nixpkgs/pull/457933 Fix for non-musl valgrind, because i totally messed up that one... Its 1 am, Can i leave that to someone else to merge when haskell eval is fixed? Or do we just force-merge? Or what is the plan here?23:57:09
3 Nov 2025
@winter:catgirl.cloudWinter sterni https://github.com/NixOS/nixpkgs/pull/452254 broke eval on -next 00:06:14

Show newer messages


Back to Room ListRoom Version: 6