on master help sign in
Block stackage-curator/stackage2nix.

Unfortunately, there is a build failure in stackage-curator and the lesser version has some compat problem which is related to the GHC version (I think!). So, I'm blocking for now. stackage2nix suffers the same fate since it relies on stackage-curator. Ping @4e6, @snoyman.

commitb2c8d1aa1b573d344789527db3c2bb3713161a37 authorLuke Murphy <lukewm@riseup.net> dateSat 9 Sep 2017, 21:02 (9 years ago) parente9d5a8d
1 file changed+3−6
build-constraints.yaml+3−6
build-constraints.yaml+3−6
@@ -281,7 +281,7 @@ packages:
281281 - persistent-postgresql
282282 - persistent-sqlite
283283 - persistent-template
284− - stackage-curator
284+ # - stackage-curator
285285 - store
286286 - stm-conduit
287287 - wai-websockets
@@ -3314,7 +3314,8 @@ packages:
33143314 - ghost-buster
33153315
33163316 "typeable.io <makeit@typeable.io>":
3317− - stackage2nix
3317+ []
3318+ # - stackage2nix
33183319
33193320 "Jeremy Huffman <jeremy@jeremyhuffman.com> @jeremyjh":
33203321 - higher-leveldb
@@ -3382,10 +3383,6 @@ packages:
33823383 - llvm-hs < 5.0.0
33833384 - llvm-hs-pure == 4.1.0.0
33843385
3385− # https://github.com/fpco/stackage-curator/issues/46
3386− - stackage-curator < 0.15.0.0
3387− - stackage2nix < 0.3.0
3388−
33893386# end of packages
33903387
33913388# Package flags are applied to individual packages, and override the values of