| 14 Aug 2025 |
 maralorn | Then there is extra-packages which gives additional versioned attributes. | 15:28:14 |
 Artem | my slight worry about configuration-hackage2nix/main.yml#extra-packages is that every package on that list has a comment saying why it's there, and it's very specific. This makes me question that it's the right place. Unless I'm expected to say "# it's a cool package not on Stakage, but I want it in nixpkgs"... | 15:28:24 |
| maralorn | And default-package-overrides which modifies which version the default attribute has. | 15:29:17 |
| Artem | but adding a package not from Stackage is shouldn't overide anything, so this field isn't applicable, right? | 15:31:41 |
| Artem | * but adding a package not from Stackage shouldn't overide anything, so this field isn't applicable, right? | 15:31:48 |
| Artem | * but adding a package not from Stackage shouldn't override anything, so this field isn't applicable, right? | 15:31:52 |
| Artem | do I need to run anything after updating configuration-hackage2nix/main.yml? the change doesn't seem to get picked up | 15:34:03 |
| maralorn | No, the field is applicable because hackage2nix always has a notion for the default. The default default is the newest version. | 15:37:06 |
 chreekat | Get it included in stackage? 🙂 | 15:37:20 |
| maralorn | Yes maintainers/scripts/haskell/regenerate-hackage-packages.nix | 15:38:01 |
| Artem | yes, I'm contemplating this now. There are some traces of it being there though: https://github.com/commercialhaskell/stackage/commit/c5e992f2a5eb9727c880e92be677d7ded665dc65 so, I guess it's just not the right LTS | 15:43:25 |
| Artem | chreekat: although I don't see it in any of the latest LTSs per GHC versions (I checked for GHC 9.10 and 9.8) | 15:45:30 |
| Artem | are you saying I should use "default-package-overrides" instead of "extra-packages" for a package outside of LTS? (I'm sorry for being slow!) | 15:46:38 |
| Artem | modulo the extension .sh, that started doing something but failed with:
Running hackage2nix to regenerate pkgs/development/haskell-modules/hackage-packages.nix …
.Regenerating transitive-broken.yaml … (pass --fast to /home/artem/nixpkgs/maintainers/scripts/haskell/regenerate-hackage-packages.sh to skip this step)
these 4 paths will be fetched (0.31 MiB download, 1.14 MiB unpacked):
/nix/store/mmi8dxjdsv8r9jxnyd3dqwqakxda1796-jq-1.8.1
/nix/store/kwxm52f2g9ap890pfj2j4ryzq2gj2i69-jq-1.8.1-bin
/nix/store/h0xayyfsl9f17bss0x1xhhz7c3n5fq43-jq-1.8.1-dev
/nix/store/1q3rqjv37glfxsmqcyvnz3ghqj1wjw4a-oniguruma-6.9.10-lib
copying path '/nix/store/1q3rqjv37glfxsmqcyvnz3ghqj1wjw4a-oniguruma-6.9.10-lib' from 'https://cache.nixos.org'...
copying path '/nix/store/mmi8dxjdsv8r9jxnyd3dqwqakxda1796-jq-1.8.1' from 'https://cache.nixos.org'...
copying path '/nix/store/kwxm52f2g9ap890pfj2j4ryzq2gj2i69-jq-1.8.1-bin' from 'https://cache.nixos.org'...
copying path '/nix/store/h0xayyfsl9f17bss0x1xhhz7c3n5fq43-jq-1.8.1-dev' from 'https://cache.nixos.org'...
error: access to absolute path '/home/artem/.local' is forbidden in restricted mode
| 15:53:55 |
| Artem | I'll have to get back to this. In the meantime, I'm submit a PR unbreaking liquid-fixpoint at least: https://github.com/NixOS/nixpkgs/pull/433722 let me know if it's horribly formatted and against the guidelines... | 16:10:30 |
| chreekat | Looks like it's under "grandfathered dependencies", so probably needs a new champion . https://github.com/commercialhaskell/stackage/blob/master/build-constraints.yaml#L5657 | 16:10:43 |
 sterni (he/him) | Artem: may be https://github.com/NixOS/nixpkgs/issues/400784, try running with --fast | 16:34:07 |
| maralorn | Yes | 17:09:10 |
| maralorn | Ah, oops. | 17:09:24 |
| Artem | --fast did fix it | 19:41:32 |
| Artem | regenerate-hackage-packages.sh seems to reformat the whole hackage-packages.nix. Am I doing something wrong? | 19:53:28 |
| maralorn | Depends on the diff?^^ | 19:54:43 |
| maralorn | Possibly you have the wrong nixfmt in scope? Not sure. | 19:55:10 |
| maralorn | Yeah, nixfmt seems to be picked up from your environment. | 19:56:35 |
| maralorn | Easiest fix is probably loading loading the shell.nix. | 19:57:31 |
| Artem | maralorn: which shell.nix? | 20:01:55 |
| Artem | oh, maybe the root of nixpkgs, let me try it | 20:03:08 |
| Artem | that did the trick, thanks! | 20:14:24 |
| Artem | chreekat: what is "grandfathered depedndencies" exactly? MAINTAINERS.md doesn't explain (other than saying you move there packages that you no longer maintain) | 20:24:18 |
| 15 Aug 2025 |
| chreekat | I think it's unmaintained (from Stackage perspective) dependencies of actively maintained packages. At one time they were included implicitly, and at some point they were made explicit. I'm not confident about that, however. | 04:44:22 |
