-
Notifications
You must be signed in to change notification settings - Fork 247
Stackage import does not work correctly for LTS-15.x #481
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
Comments
I'm also affected by this bug and created a reproduction that only requires cloning a repo running a script. |
Ahh, does this explain why I'm getting errors like |
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>
.
|
From a quick glance it seems like |
@codygman I've opened a PR against |
@serras that looks conceptually correct. |
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 To have nix understand this world, we'll translate all of hackage to nix (hackage.nix), stackage (stackage.nix), and cabal plans. All via 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. |
@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 |
@serras @codygman As a workaround, you can use LTS-15 if you add this set to your package set's
This works by forcing all GHC boot packages to be copied from the global package database, as described in #524 |
Which LTS/nightly snapshot? |
@angerman Sorry, I was really asking what else was needed to get builds working with LTS-15.x. |
@TravisWhitaker ahh I see the LTS's didn't update as expected in stackage.nix :-/ Guess I'll have to hand intervene again. |
@angerman I think the LTS files in stackage.nix are correct, but builds with LTS-15 are failing for the reason identified in #524. Run something like
|
@TravisWhitaker I believe the issues is that since input-output-hk/nix-tools#83, the LTS-15 expressions in stackage.nix haven't been regenerated. |
@angerman the expressions generated for nightlies after input-output-hk/nix-tools#83 don't work either, also because of #524:
|
I have an idea how to override Cabal in stackage, will play around tomorrow. |
Here's a patch that was made for stack2nix: nh2/stack2nix@c009e33#diff-5cecbf2a44d1043802f1c0377b4f1a7cR210 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The automatically-generated
.nix
files for Stackage LTS until 14.x contain the bundled packages, likestm
, both in thecompiler
section and as a regular package. Alas, from 15.x, the packages in thecompiler
section are not found as regular packages. That means that if you depend on one of those packages (we do in particular depend onstm
) the build fails.I am happy to provide a PR on this with some guidance :)
The text was updated successfully, but these errors were encountered: