| 11 Apr 2026 |
alexfmpe | I'm also wondering whether addTestToolDepend self.buildHaskellPackages.hspec-discover is what we should always do or if there's a point to this (commented) conditional: https://github.com/NixOS/nixpkgs/blob/86ab6aea5099ecae02ef2331cfd3f1d53362f1db/pkgs/development/haskell-modules/configuration-common.nix#L1209 | 23:07:57 |
| 12 Apr 2026 |
sterni | I don’t think so. do you have some examples? I have a suspicion, but would need to check. | 07:41:57 |
| leona changed their profile picture. | 12:15:40 |
alexfmpe | all of these build on haskellPackages but need that override on pkgsStatic.haskellPackages
https://github.com/alexfmpe/nixpkgs/blob/27752ed2109458fdc93a0917123f9566920c13e6/pkgs/development/haskell-modules/configuration-nix.nix#L2271-L2287 | 13:28:44 |
alexfmpe | $ nix-shell default.nix -A haskellPackages.say --run 'hspec-discover'
Usage: hspec-discover SRC CUR DST [--module-name=NAME]
$ nix-shell default.nix -A pkgsStatic.haskellPackages.say --run 'hspec-discover'
/tmp/nix-shell-3496921-3747326576/rc: line 3: hspec-discover: command not found
| 13:31:18 |
sterni | A the answer is likely that these packages depend on hspec which depends (not build-tool-depends!) on hspec-discover which gets propagated and is executable when natively compiling | 21:07:24 |
sterni | e.g. say has the packaging bug that it doesn't declare the dependency at all, should be using build-tool-depends. | 21:07:48 |
sterni | we have a hack in cabal2nix that fixes if you use build-depends : hpsec-discover, but if you don't declare the dep at all, it's problematic of course | 21:08:13 |
alexfmpe | Ah, guess the hack hid the problem | 21:52:17 |
alexfmpe | So the fix here is to PR those addFooToolDepends unconditionally yeah? | 21:52:39 |
alexfmpe | (well, the non-upstream fix) | 21:53:42 |
alexfmpe | * Ah, guess the hack masks the problem | 21:54:22 |
alexfmpe | https://github.com/NixOS/nixpkgs/pull/509371 | 23:41:54 |
| 13 Apr 2026 |
sterni | In reply to @alexfmpe:matrix.org Ah, guess the hack masks the problem the hack solves the problem, but in this case the package doesn’t declare the dependency at all | 10:31:40 |
sterni | In reply to @alexfmpe:matrix.org So the fix here is to PR those addFooToolDepends unconditionally yeah? yes | 10:31:48 |
| 14 Apr 2026 |
| M̸̙̜̔̇Ǎ̴͎̙͔G̸̞̈N̸͔͍̝͗͋̾Ő̷͖̼͈̽̚L̷̻͚̓̔I̷̛͔̰̟̔Å̴̩̍ ̷̦̒̇͝M̷̱̠̺̉̎A̵̼̎͗͘Ỹ̸̬̲͂̕H̷̙̖͂Ē̷͉̦̌͒M̶͈̥̽̐ Houston, we've had a Microsoft changed their display name from M̸̙̜̔̇Ǎ̴͎̙͔G̸̞̈N̸͔͍̝͗͋̾Ő̷͖̼͈̽̚L̷̻͚̓̔I̷̛͔̰̟̔Å̴̩̍ ̷̦̒̇͝M̷̱̠̺̉̎A̵̼̎͗͘Ỹ̸̬̲͂̕H̷̙̖͂Ē̷͉̦̌͒M̶͈̥̽̐ (you don't get my real name) to M̸̙̜̔̇Ǎ̴͎̙͔G̸̞̈N̸͔͍̝͗͋̾Ő̷͖̼͈̽̚L̷̻͚̓̔I̷̛͔̰̟̔Å̴̩̍ ̷̦̒̇͝M̷̱̠̺̉̎A̵̼̎͗͘Ỹ̸̬̲͂̕H̷̙̖͂Ē̷͉̦̌͒M̶͈̥̽̐ Houston, we've had a Microsoft. | 15:59:50 |
alexfmpe | how can I turn on strictDeps by default on the package set? I'd like to locally build maintained or so against it to catch them all in one go | 16:33:26 |
alexfmpe | I mean, I can use my local nixpkgs config and all, but presumably we'd like to also enable the flag by default once fixed? | 16:34:03 |
alexfmpe | ah, I can jam it right in our call to mkDerivation | 16:50:14 |
alexfmpe | what's the actual command whose results https://github.com/cdepillabout/nix-haskell-updates-status is looking at? | 17:51:33 |
Alex | Curiously, I don't seem to have been pinged by those mentions. Perhaps because they are in the code and not the Git objects.
Microhs cross and musl Hugs being broken are things I was already aware of, so not really a big deal.
| 20:03:52 |
alexfmpe | actually, what I want is exactly the list of successes of that build summary and build them all with strictDeps | 23:22:54 |
alexfmpe | ok got the .json from hydra-report, I'll jq something up | 23:28:57 |
| 15 Apr 2026 |
| crop joined the room. | 16:14:55 |
crop | i want to use a tool packaged with cabal. the specification file is too strict to run with current haskel from nixpkgs.
i get the error that a library is not available but it is available just too new.
so i would like to loosen the bounds.
i did this by changing the cabal file and with this the program compiles.
i would prefer to not change the cabal file and loosen the condition somehow differently. is this possible with nix? | 16:51:54 |
alexfmpe | you can doJailbreak, e.g. https://github.com/NixOS/nixpkgs/blob/608994ab06334b0b4580aa3267a19f91c16bb613/pkgs/development/haskell-modules/configuration-common.nix#L2495 | 18:36:41 |
alexfmpe | though long-term it's best to PR the cabal file modification to the tool | 18:37:24 |
alexfmpe | so you won't need to have a doJailbreak around | 18:37:36 |
alexfmpe | $ jq '.[2] | map(select((.buildstatus == 0) and (.job | contains("haskellPackages") and (contains("pkgsCross") | not) and (contains("pkgsMusl") | not) and (contains("pkgsStatic") | not))) .job)' ~/.cache/haskell-updates-build-report.json | wc -l
7395
| 22:32:00 |
alexfmpe | $ jq '.[2] | map(select((.buildstatus == 0) and (.job | contains("haskellPackages") and (contains("pkgsCross") | not) and (contains("pkgsMusl") | not) and (contains("pkgsStatic") | not))) .job)' ~/.cache/haskell-updates-build-report.json | head -n 5
[
"haskellPackages.AC-Angle.x86_64-linux",
"haskellPackages.AC-Colour.x86_64-linux",
"haskellPackages.AC-Boolean.x86_64-linux",
"haskellPackages.AC-PPM.x86_64-linux",
| 22:32:13 |