| 10 Oct 2025 |
maralorn | (Or alas, I totally did but now I feel bad about it.) | 21:36:32 |
dotlambda | I'll first take the easy way. And try the harder one later, when I feel like running nixpkgs-review etc | 21:37:09 |
| 11 Oct 2025 |
Collin Arnett | Does overrideSrc include new data-files? I'm getting a "No such file or directory" when I try and override based on a fork I'm working on. | 17:23:37 |
sterni | Nix does not need to know about data files specifically, so shouldn't make a difference | 18:13:12 |
| 12 Oct 2025 |
Collin Arnett | Ah yeah I just needed to do a cabal clean. Thanks for confirming 🙂 | 04:49:44 |
chreekat | Seems buggy on cabal's side | 08:13:51 |
chreekat | Inputs changed, build should have been invalidated... | 08:14:16 |
| lep joined the room. | 09:27:30 |
Collin Arnett | Yeah that's why I was pulling my hair out so much! I saw the rebuild happen on the nix side and I assumed everything would be good from there after another cabal recompile. | 16:59:09 |
| 14 Oct 2025 |
| @tianyi:superkazuya.com left the room. | 04:18:45 |
| @jellyterra:matrix.org left the room. | 11:29:27 |
| 16 Oct 2025 |
| @sasha:the-apothecary.club left the room. | 01:51:05 |
chreekat | Is it reproducible? Could you open a ticket on the cabal issue tracker? | 07:03:00 |
| 17 Oct 2025 |
eldritchcookie | given a haskellPackageSet like haskellPackages or haskell.packages.ghc912 how do i apply an overlay to the package set only? | 12:02:20 |
eldritchcookie | looking at haskell-flake source code gave me an answer .extend make it take a overlay. | 12:24:51 |
eldritchcookie | do i need to rename the package if i pass it as another name like
gi-gtk-hs = pkgs.haskell.lib.markUnbroken (super.gi-gtk-hs.override {
gi-gtk = self.gi-gtk3;
gi-gdk = self.gi-gdk3;
});
| 12:30:15 |
| 18 Oct 2025 |
| @ihar.hrachyshka:matrix.org left the room. | 00:13:02 |
MangoIV | Redacted or Malformed Event | 10:36:07 |
MangoIV | * are you aware that nixpkgs unstable currently shipos incompatible hls and cabal-install versions? | 10:36:18 |
MangoIV | * are you aware that nixpkgs unstable currently ships incompatible hls and cabal-install versions? | 10:36:22 |
maralorn | No, wdym? | 10:39:38 |
MangoIV | maybe that's not correct - I don't know how to interpret certain things - there's an issue about 2.11 being incompatible with 3.16 but as a fix it is recommended to build 2.11 with 3.16 (??)
but in fact, if you open a project that currently doesn't type check, cabal repl barfs you in the face (I do not expect the cradle to invoke cabal repl, fwiw) maybe it's actually an incompatibility between 3.16 and hie-bios? | 10:41:26 |
MangoIV | I'm not sure | 10:41:29 |
MangoIV | that can't be it though, hie-bios is up to date in nixpkgs | 10:42:19 |
MangoIV | I think I know what's going on | 10:44:34 |
MangoIV | let me check | 10:44:47 |
MangoIV | jup - the reason is that older nixpkgs versions ship hie-bios which is not of the required version for hls 2.11.0.0 but hls is in fact compatible with both (no version bump) so if you resolve hie-bios to <0.17, hls to 2.11.0.0 and cabal-install 3.16 it will build but it will be broken at runtime. Very cool | 10:57:04 |
MangoIV | version bumps for breaking changes? I don't think so. | 10:57:20 |
maralorn | @mangoiv.:matrix.org I am currently too tired to fully grasp that. (Will read again later) But a) can this also happen with hls 2.12? And b) the best fix is to make sure we ship hie-bios >= 0.17? | 15:47:41 |
maralorn | Huh, after crossreading in the HLS room, this looks like something a distribution should not screw up. I remember reading the compat issue in the cabal release but it didn't occur to me that I would have to look out for it. Damn it | 15:51:28 |