| 23 Sep 2025 |
|  yliceee changed their profile picture. | 20:04:24 |
| 24 Sep 2025 |
|  Magnolia Mayhem changed their profile picture. | 14:46:16 |
| Magnolia Mayhem changed their profile picture. | 19:45:13 |
| 25 Sep 2025 |
 bglgwyng | If a package is not affected by foo-package.override { random = ... }, which means random is not overridden but remains as the one in haskellPackages, what are some things I can try to investigate further | 08:53:03 |
| bglgwyng | The package overrides other than random works well | 08:53:22 |
| bglgwyng | * If a package is not affected by foo-package.override { random = ... }, which means random is not overridden but remains as the one in haskellPackages, what are some things I can try to investigate further? | 09:00:44 |
 maralorn | I can’t think of anything straightforward. Best ideas is a) there is a second override which negates your first override b) you are mistakingly not actually passing a different random. I can think of wilder theories, but they will be even more likely to be wrong. | 09:30:59 |
| bglgwyng | I tried overriding it at the last place like,
{ packages.hip = config.cabal-projects.default.packages.hip.override { random = config.cabal-projects.default.packages.random; }; }
but still same
| 09:32:13 |
 sterni | bglgwyng: Haskell dependencies need to be propagated, so any given package sees its transitive Haskell dependency closure. random is pretty common, so probably somewhere the non overridden random is visible. Cabal is free to pick any version within bounds. | 10:58:17 |
