| 20 Feb 2026 |
 sterni | the code gen and execution part means that we have little confidence it will work at runtime which the test suite helps with | 12:54:51 |
| 21 Feb 2026 |
 woobilicious | sterni: the maintainer doesn't think the patch is a good idea, doesn't think we'd need to run tests, we'd still need to package mathsat, and any other SAT solvers nixpkgs is missing, it's way too much effort for a package that no one is using. I agree that it would be nice to run but the return on maintenance burden isn't there. | 01:49:34 |
| woobilicious | the other issue is we really shouldn't mark the package broken when say, the cvc5 tests are failing, when A user might have no interest in using cvc5 backend, and only the z3 backend. | 01:55:13 |
| woobilicious | Error in option parsing: Cannot use --nl-cov without configuring with --poly. This is a cvc5 test that fails for example. | 01:56:33 |
|  Void Mona(d) changed their display name from Uraraka ~ Ochaco to Void Mona(d). | 14:31:16 |
|  h7x4 changed their profile picture. | 19:25:58 |
| h7x4 changed their profile picture. | 19:30:15 |
| h7x4 changed their profile picture. | 19:33:40 |
| 22 Feb 2026 |
|  Kite joined the room. | 02:54:14 |
 aiya | so for this section of the maintainer guide, and the fact that the filter for current PRs (https://github.com/nixos/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Ahaskell-updates) includes head:haskell-updates, does that imply any PR must start with haskell-updates? or not (https://github.com/NixOS/nixpkgs/pull/487958)? | 05:50:21 |
 Alex | I don't know how GitHub's PR rules work, but I believe head:haskell-updates filters for all PRs targeting the haskell-updates branch.
The Nixpkgs convention for PR titles is to title them with the affected package.
My PR there is a bit of an irregular one because while it does modify a ghc package (pkgsCross.riscv64.haskell.compiler.ghc94), it does not touch the default ghc.
It targeted haskell-updates because it was a fix to a regression in a build checked by Hadrian. | 06:10:16 |
 hellwolf | hmm, what happens to https://nixpk.gs/pr-tracker.html?pr=485516 ? | 15:32:43 |
 alexfmpe | I don't understand the question | 15:55:58 |
| hellwolf | sorry for my Sunday laconism :p
I meant to ask when will that haskell-updates PR be merged to master/nixpkgs-unstable? | 17:33:04 |
 maralorn | Well, when it's finished. 😆 I have no clue if there is a holdup on staging-next. Coordination around that question happens in the staging chat room. | 17:41:07 |
| aiya | i understand that PR titles are for the affected titles but my question is for conventions on branch names: if i want to merge a PR into haskell-updates, what should my branch name be? must it start with haskell-updates? (i.e. haskell-updates-fix-pkg versus fix-pkg
I believe head:haskell-updates filters for all PRs targeting the haskell-updates branch
i believe that would be base:haskell-updates, head filters on your branch name | 22:41:57 |
| maralorn | aiya: I am not aware of any rule. At least when you are opening the PR from your fork. | 22:50:49 |
| 23 Feb 2026 |
 Acid Bong | In reply to @aiya:catgirl.cloud
i understand that PR titles are for the affected titles but my question is for conventions on branch names: if i want to merge a PR into haskell-updates, what should my branch name be? must it start with haskell-updates? (i.e. haskell-updates-fix-pkg versus fix-pkg
I believe head:haskell-updates filters for all PRs targeting the haskell-updates branch
i believe that would be base:haskell-updates, head filters on your branch name your branch name doesn't matter at all, only commit and PR description and contents | 20:12:06 |
| Acid Bong | * your branch name doesn't matter at all, only commit and PR description and contents, and the branch you're targeting | 20:13:29 |
|  Luke changed their display name from magpi to Luke Worth. | 21:17:08 |
| Luke changed their display name from Luke Worth to Luke. | 21:17:40 |
| 24 Feb 2026 |
|  Jack​ changed their profile picture. | 03:32:21 |
