fix hypergiant overrides

[r14c]

chicken-hypergiant was marked as broken, I updated the overrides so it would build again.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[nix-owners]

The PR's base branch is set to master, but 7677 commits from the release-24.11 branch are included. Make sure you know the right base branch for your changes, then:

• If the changes should go to the release-24.11 branch, change the base branch to release-24.11
• If the changes should go to the master branch, rebase your PR onto the merge base with the master branch:

  # git rebase --onto $(git merge-base upstream/master HEAD) $(git merge-base upstream/release-24.11 HEAD)
  git rebase --onto 1d95cb5fa7a38717172e090d54338ca8daef8a86 f0946fa5f1fb876a9dc2e1850d9d3a4e3f914092
  git push --force-with-lease

[r14c]

tested by building the demo example given in the hypergiant docs.

[r14c]

@corngood @konst-aa @nagy Sorry to bother, I'm new to contributing to nixpkgs. Any pointers you could give me to help this patch get merged?

[nagy]

You seem to be targeting more than just hypergiant. I would say a good start would be to have one commit for each package modification with a commit message as described here:

https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#commit-conventions

Thanks for the help.

[konst-aa]

Hey, welcome!!

Thank you for putting up this contribution! I'd like to echo what Nagy said. Breaking up your PR into one commit per package + the naming conventions is the only thing missing right now. Then, I'll check if it builds on various systems. I'm about to get an Apple Silicon laptop, so I could also test it on Arm Darwin.

[r14c]

OK that makes sense. Fix up all of hypergiant's broken dependencies, then fix hypergiant itself.

[konst-aa]

@wolfgangwalther @r14c Hey, following up. Thanks again for contributing! If you think it's ready, all that's missing is collapsing the commits and having them follow nixpkgs convention. You can find the examples for chicken in previous PRs / commits to files in ...compilers/chicken/5