static-haskell-nix
static-haskell-nix copied to clipboard
Bump to nixpkgs-21.11
This PR bumps to nixpkgs-21.11 (https://github.com/NixOS/nixpkgs/commit/573095944e7c1d58d30fc679c81af63668b54056), which contains LTS-18.17 and uses ghc-8.10.7.
This PR fixes or disables all the packages in working
and workingStackageExecutables
, so ci.nix
should succeed.
I started working on this because I wanted to use static-haskell-nix for one of my personal projects, which is based on nixpkgs-21.11.
@nh2 In the past it looks like static-haskell-nix has followed Nixpkgs master
(not one of the release branches). This PR changes static-haskell-nix to use 21.11. However, the 21.11 branch-off has just occurred, so I imagine most of the changes in this PR would also be necessary if the latest master
was used instead.
@nh2 This should be ready for review now.
I a CI build of one of your older pushes, commit
6e3e1df, ran through with working
working but others not yet: https://buildkite.com/nh2/static-haskell-nix/builds/1024
Started one with the newer commits here:
- ~https://buildkite.com/nh2/static-haskell-nix/builds/1028~
- ~https://buildkite.com/nh2/static-haskell-nix/builds/1029~
- https://buildkite.com/nh2/static-haskell-nix/builds/1030
@nh2 With 3d0be9a, I'm hoping that now ci.nix
should be fully working.
Looking at buildkite, it looks like stack2nix-example
and static-stack
pipelines are failing because of ghc8104
no longer existing in Nixpkgs. For instance, in https://buildkite.com/nh2/static-haskell-nix/builds/1030#41e2a511-8117-4ed6-86d6-3312731206d9.
I'm not personally interested in using/fixing either of these, so I don't know if you'd be willing to merge this PR with those still failing. But if not, maybe we could keep this PR open and someone who is interested in those could use this PR as a base to start hacking on them.