-
Notifications
You must be signed in to change notification settings - Fork 111
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
haste-boot problems. #399
Comments
OK, tested my repro a bit more, just to be sure. Dockerfile:
script:
What to run:
|
I believe the Apart from this (probable) workaround, I'd say that the long term fix is to get Haste support into cabal and stack proper. |
As you can see from my first post on this topic, things go considerably better with the stack-exec than without; please compare the two really big blobs in my original post. |
It seems that running |
as a data point, I ran "cabal update" then "stack exec -- haste-boot --force --local" worked ok. |
This may be related to #395
After "stack install" on the master branch, haste-boot fails in a catastrophic "cabal is broken" sort of way.
Here's the output:
Running "stack exec haste-boot -- --force --local" does better, but still fails:
And to repro this we have:
The Dockerfile I used, sort of; this is actually an unrolling of several stacked Dockerfiles, but it should be close enough, as everything else is personal environment tweaking:
stack.repo there is:
The docker is being run like so:
And then once that was up my entire history is:
The text was updated successfully, but these errors were encountered: