!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

721 Members
For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://haskell4nix.readthedocs.io/ | More Nix: #community:nixos.org | More Haskell: #haskell-space:matrix.org145 Servers

Load older messages


SenderMessageTime
8 Apr 2025
@maralorn:maralorn.demaralornWe should instead increase the merge frequency. again.13:45:49
@maralorn:maralorn.demaralornOur goal normally is once every one or two weeks.13:46:02
@maralorn:maralorn.demaralornThis has gotten ridiculous.13:46:11
@maralorn:maralorn.demaralornBut speaking of: Can someone explain to me why our branch hasn’t been checked by hydra for three days?13:46:39
@maralorn:maralorn.demaralornhttps://hydra.nixos.org/jobset/nixpkgs/haskell-updates#tabs-evaluations13:47:03
@maralorn:maralorn.demaralornLast check: 04-05, but configuration says every 8 ours.13:47:25
@emilazy:matrix.orgemily"Check interval: -28800" means only manually, I think.14:01:54
@emilazy:matrix.orgemily probably vcunat tweaked it because the queue is huge right now and we need to do -next cycles before release 14:02:08
@vcunat:matrix.orgvcunatI haven't touched it recently.14:02:50
@vcunat:matrix.orgvcunatBut it's possible that it's some long leftover.14:03:05
@vcunat:matrix.orgvcunatThough in that case someone must've been triggering those evals.14:03:34
@vcunat:matrix.orgvcunat* Though in that case someone must've been triggering those evals manually.14:03:41
@vcunat:matrix.orgvcunat(which I did now)14:04:34
@vcunat:matrix.orgvcunat* (which I did right now)14:04:42
@maralorn:maralorn.demaralorn Oh, true. Looks like sterni has been triggering them manually. 14:04:51
@maralorn:maralorn.demaralornWhich is actually kinda fine for me. But I need to know it’s the case. 😄14:05:05
@vcunat:matrix.orgvcunatDo you want trigger permissions?14:05:30
@vcunat:matrix.orgvcunatI don't mind adjusting the settings, too.14:06:33
@vcunat:matrix.orgvcunat We just need to share Hydra's resources reasonably. I'm not aware of a big hurry with staging-next right now even. 14:07:59
@vcunat:matrix.orgvcunatToday even all kind of changes are allowed in staging (theoretically). Tomorrow is the first small freezing step, but there's ample time after it.14:10:55
@alexfmpe:matrix.orgalexfmpehuh shouldn't we merge haskell-updates ASAP given staging window for 25.05 is closing fast?14:12:43
@vcunat:matrix.orgvcunat My reading of the schedule is that breaking changes (e.g. in haskell packages) are allowed up to 2025-04-23. 14:19:27
@vcunat:matrix.orgvcunatNon-breaking mass rebuilds up to some early May.14:20:14
@vcunat:matrix.orgvcunatBut well - in the worst case, important fixes get backported to stable continually.14:20:48
@sternenseemann:systemli.orgsterni (he/him)We just need to meet the window for breaking changes in staging, shouldn't be a problem fingers crossed14:48:11
@hellwolf:matrix.orghellwolfthanks folks. I have been free riding your work. I should really contribute some, since I do believe I am able to. I just need to plan the time for this.15:32:28
@maralorn:maralorn.demaralornWe have them, don’t worry.15:44:38
@alexfmpe:matrix.orgalexfmpeThose regressions on cabal might be annoying, and bumping cabal means rebuild right? Maybe we just bump cabal itself to 3.14.2 and then merge and go back to normal flow?17:55:53
@alexfmpe:matrix.orgalexfmpe* Those regressions on cabal might be annoying, and bumping cabal means mass rebuild right? Maybe we just bump cabal itself to 3.14.2 and then merge and go back to normal flow?17:56:08
@maralorn:maralorn.demaralornBumping cabal-install is not a mass rebuilt. Bumping Cabal is not a thing since it's bundled with ghc.21:59:18

Show newer messages


Back to Room ListRoom Version: 6