| 25 Jun 2025 |
 maralorn | In reply to @le:4d2.org
Success! I had to also disable the Tests since they also do not work (and seem pretty unfixable to me), but with this abomination of a nix-shell command, it builds!
nix-shell -p 'haskellPackages.ghcWithPackages (p: with haskell.lib; [(unmarkBroken (dontCheck (doJailbreak p.haskore)))])'
Is this a solution worth pushing to the repo, or is the usage of doJailbreak and dontCheck too ugly?
No, that's uptreamable. Imagine how much time you can save the next you without them even realizing. | 11:44:29 |
| maralorn | In reply to @ners:nixos.dev
I like to encourage people to use unmarkBroken rather than markUnbroken, as the flag is called broken, not unbroken. 🙃 I have grown quite fond of that little wart. | 11:44:53 |
 lambdatheultimatealias | In reply to @sternenseemann:systemli.org
lambdatheultimatealias: note that you can't draw any conclusions from nixpkgs about hackage since we regularly apply patches, modify constraints, build flags, test flags etc. Makes sense. If I follow correctly Hackage just provider the default version and sources which can be overridden depending on stackage and nixpkgs. | 11:59:14 |
 sterni | Hackage is just a place for maintainers to upload their packages. Metadata (e.g. constraints) can be edited by maintainers and Hackage trustees after the fact. Hackage makes no statement about which version to use which is the job of the cabal solver or tools like stack(age) | 12:02:24 |
 Alex | In reply to @ners:nixos.dev
I like to encourage people to use unmarkBroken rather than markUnbroken, as the flag is called broken, not unbroken. 🙃 I didn't even realise there were two functions for it... | 12:55:45 |
 alexfmpe | Aren't there 4? | 16:19:31 |
| alexfmpe | Two names each for turning it on and ofd | 16:19:42 |
| alexfmpe | * Two names each for turning it on and off | 16:19:59 |
| maralorn | In reply to @alexfmpe:matrix.org
Aren't there 4? I think in that sense there are 3. Because markBroken cannot not have the un in different places | 16:41:06 |
| alexfmpe | Huh I assumed there was unmarkUnbroken | 16:43:27 |
| alexfmpe | Can't we just deprecate one of them and end this? | 16:43:42 |
| maralorn | We totally could. But I like them too much to do it myself. 😂 | 16:46:56 |
| maralorn | What the heck is the correct way to run doctests in a nixpkgs package? | 21:20:33 |
| maralorn | cabal repl --with-compiler=doctest does not work because the doctest does not have the same pkg db than the ghc used by cabal. | 21:21:10 |
| sterni | cabal exec -- cabal repl --with-compiler=doctest maybes | 22:16:44 |
| sterni | * cabal exec -- cabal repl --with-compiler=doctest maybe? | 22:16:46 |
| maralorn | Still the same problem:
Configuring library for status-script-0.1.0.0...
Loaded package environment from /home/maralorn/git/config/packages/status-script/dist-newstyle/tmp/environment.-175358/.ghc.environment.x86_64-linux-9.8.4
<command line>: cannot satisfy -package-id aeson-2.2.3.0-2mnLs4rnok4A0ksXaTX6dm
and I am relatively certain that is because cabal-install does use a different ghc pkg db.
| 22:34:42 |
| maralorn | * Still the same problem:
Configuring library for status-script-0.1.0.0...
Loaded package environment from /home/maralorn/git/config/packages/status-script/dist-newstyle/tmp/environment.-175358/.ghc.environment.x86_64-linux-9.8.4
<command line>: cannot satisfy -package-id aeson-2.2.3.0-2mnLs4rnok4A0ksXaTX6dm
and I am relatively certain that is because cabal-install does use a different ghc pkg db than doctest.
| 22:34:46 |
| maralorn | So this seems to me that we should maybe patch doctest so that it picks up the package db from the ghc.withPackages it is used from? | 22:35:25 |
| 26 Jun 2025 |
| sterni | ah yes I remember https://github.com/haskell/cabal/issues/7792#issuecomment-2124304244 | 21:25:04 |
