Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hackage: update all-cabal-hashes snapshot #34870

Merged
merged 1 commit into from Feb 20, 2018

Conversation

gwils
Copy link
Contributor

@gwils gwils commented Feb 12, 2018

I'm not sure how to test this but if somebody can point me to how, I'm happy to do so.

Motivation for this change

I'd like more up-to-date hackage packages available from callHackage

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@adisbladis
Copy link
Member

cc @peti

@peti peti merged commit 17bc189 into NixOS:master Feb 20, 2018
@gwils
Copy link
Contributor Author

gwils commented Feb 20, 2018

Thanks @peti

Please see also #34871

@gwils gwils deleted the update-all-cabal-hashes branch February 20, 2018 09:27
@gwils
Copy link
Contributor Author

gwils commented Feb 22, 2018

Thanks again @peti !

Is there a way to automate this so that it is updated more frequently? Alternatively, I can keep making pull requests like this one whenever there are changes that I would like nix to know about.

@peti
Copy link
Member

peti commented Feb 26, 2018

I've added a small script that will update the hash every couple of says in master. I haven't automated anything to that extend in any of the release branches, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants