Stackage import does not work correctly for LTS-15.x

[serras]

The automatically-generated .nix files for Stackage LTS until 14.x contain the bundled packages, like stm, both in the compiler section and as a regular package. Alas, from 15.x, the packages in the compiler section are not found as regular packages. That means that if you depend on one of those packages (we do in particular depend on stm) the build fails.

I am happy to provide a PR on this with some guidance :)

[codygman]

I'm also affected by this bug and created a reproduction that only requires cloning a repo running a script.

[dhess]

Ahh, does this explain why I'm getting errors like error: The Haskell package set does not contain the package: text (build dependency). when trying to build against LTS-15?

[serras]

That's my guess, but until we don't produce a patch, it's hard to say 100% sure. El dom., 22 mar. 2020 10:13, Drew Hess <notifications@github.com> escribió:

…

Ahh, does this explain why I'm getting errors like error: The Haskell package set does not contain the package: text (build dependency). when trying to build against LTS-15? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#481 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACLQVXAEW4ZEHMLB7OO23DRIXJCJANCNFSM4LEZJBAA> .

[zimbatm]

From a quick glance it seems like ghc-boot-packages should use the packages from the compiler section. But it's hard to tell, this project is really complicated.

[serras]

@codygman I've opened a PR against nix-tools input-output-hk/nix-tools#83 Unfornately, I cannot check that it works on my current machine, could you try using your repo and check whether it actually solves the problem?

[angerman]

@serras that looks conceptually correct.

[angerman]

But it's hard to tell, this project is really complicated.

It tries to be very simple at the core, but there are so many edge cases.

The high level overview is this: we either have a stack project, or a cabal project. Both lead to a solution of packages to be used. For stack this is the curated package set. For cabal, this is what ever cabal configure computes and provides through the plan.json file.
The recent switch in stackage's format (introduces for LTS-15+), did drop the compiler packages from the plan.

To have nix understand this world, we'll translate all of hackage to nix (hackage.nix), stackage (stackage.nix), and cabal plans. All via nix-tools from some non-nix description to a nix-description. nix-toolss only purpose is to translate into something nix can understand.

Finally haskell.nix will then tie it all together in the nix world. (potentially calling out to nix-tools and IFDing expressions that can not be reasonably pre-computed. For example computing, and translating plan.json with cabal and nix-tools).

One general goal is to abstract cabal and stack away, such that the inputs to haskell.nix are of the same shape. It shouldn't make a difference if the curated package set was pre-computed (stack), or computed on demand (cabal). haskell.nix should only have to know about package sets.

[TravisWhitaker]

@angerman Now that input-output-hk/nix-tools#83 is merged, what needs to be done to fix this up in haskell.nix? I too am stuck on errors of the form error: The Haskell package set does not contain the package: text (build dependency)..

[TravisWhitaker]

@serras @codygman As a workaround, you can use LTS-15 if you add this set to your package set's modules list:

{ nonReinstallablePkgs =                                                                                                                                                                      [64/94]
                [ "rts"
                  "ghc-heap"
                  "ghc-prim"
                  "integer-gmp"
                  "integer-simple"
                  "base"
                  "deepseq"
                  "array"
                  "ghc-boot-th"
                  "pretty"
                  "template-haskell"
                  "ghcjs-prim"
                  "ghcjs-th"
                  "ghc-boot"
                  "ghc"
                  "Cabal"
                  "Win32"
                  "array"
                  "binary"
                  "bytestring"
                  "containers"
                  "directory"
                  "filepath"
                  "ghc-boot"
                  "ghc-compact"
                  "ghc-prim"
                  "ghci"
                  "haskeline"
                  "hpc"
                  "mtl"
                  "parsec"
                  "process"
                  "text"
                  "time"
                  "transformers"
                  "unix"
                  "xhtml"
                  "stm"
                  "terminfo"
                ];
            }

This works by forcing all GHC boot packages to be copied from the global package database, as described in #524

[angerman]

@angerman Now that input-output-hk/nix-tools#83 is merged, what needs to be done to fix this up in haskell.nix? I too am stuck on errors of the form error: The Haskell package set does not contain the package: text (build dependency)..

Which LTS/nightly snapshot?

[TravisWhitaker]

@angerman Sorry, I was really asking what else was needed to get builds working with LTS-15.x.

[angerman]

@TravisWhitaker ahh I see the LTS's didn't update as expected in stackage.nix :-/ Guess I'll have to hand intervene again.