Stack hoogle commands fails due to not finding/installing hoogle #4905
Comments
|
I'm running into the same issue. |
|
I don't know whether this might be the cause, but after running so maybe this error gets masked when running |
|
No, that is not the case. I even removed a local hoogle version I had, and the command still fails. |
|
Somehow the which is not in my |
|
@dnadales your build problem seems to be about conflicting dependencies: |
|
@dnadales #4958 should resolve the problem of finding automatically installed hoogle but it won't resolve the problem with hoogle dependencies, there is a workaround for that - add |
|
Thanks. Don't worry about the dependency problem. It was a red herring.
Sorry about that.
I'm going to check the link you referred to.
…On Sat, Jul 13, 2019, 12:38 Kirill Zaborsky ***@***.***> wrote:
@dnadales <https://github.com/dnadales> #4958
<#4958> should resolve the
problem of finding automatically installed hoogle but it won't resolve the
problem with hoogle dependencies, there is a workaround for that - add
haskell-src-exts-1.21.0 as an extra dep or use nightly-2019-07-13.
@snoyberg <https://github.com/snoyberg> do you remember why do we install
the latest Hoogle version? Currently it's only compatible with latest
nightlies and none of LTS snapshots which makes stack hoogle broken.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4905?email_source=notifications&email_token=AABKZU565HTNZCFASZJ5VQLP7GWAVA5CNFSM4H3DEOCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3PDYA#issuecomment-511111648>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABKZU2LM6EE4KGHDPMM6CDP7GWAVANCNFSM4H3DEOCA>
.
|
|
I don't know why it's set up that way, and I don't think it's the right
approach.
On Sat, Jul 13, 2019, 1:43 PM Damian Nadales <[email protected]>
wrote:
… Thanks. Don't worry about the dependency problem. It was a red herring.
Sorry about that.
I'm going to check the link you referred to.
On Sat, Jul 13, 2019, 12:38 Kirill Zaborsky ***@***.***>
wrote:
> @dnadales <https://github.com/dnadales> #4958
> <#4958> should resolve
the
> problem of finding automatically installed hoogle but it won't resolve
the
> problem with hoogle dependencies, there is a workaround for that - add
> haskell-src-exts-1.21.0 as an extra dep or use nightly-2019-07-13.
> @snoyberg <https://github.com/snoyberg> do you remember why do we
install
> the latest Hoogle version? Currently it's only compatible with latest
> nightlies and none of LTS snapshots which makes stack hoogle broken.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#4905?email_source=notifications&email_token=AABKZU565HTNZCFASZJ5VQLP7GWAVA5CNFSM4H3DEOCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3PDYA#issuecomment-511111648
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AABKZU2LM6EE4KGHDPMM6CDP7GWAVANCNFSM4H3DEOCA
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4905?email_source=notifications&email_token=AAAMCB67TJICBQR3MLMAG4TP7GWVNA5CNFSM4H3DEOCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3PGHA#issuecomment-511111964>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAMCB54TCQ5BL55TJJ32ADP7GWVNANCNFSM4H3DEOCA>
.
|
|
Sorry to bother again, any ideas on when #4958 will be merged? And is there a workaround I could use in the meantime? To be clear, the dependencies are fine, every builds, but then the |
|
@dnadales did you try Stack with #4958 applied? While the PR will fix the problem for LTS-14 it won't work with LTSes before that and could break because of future hoogle updates. I'll create a PR with installing hoogle from spanshot and that should be a proper fix. Regarding this partial fix - I'm not quite sure why it wasn't yet merged |
|
No I didn't. Would this work if I build stack with #4958 and run the generated binary (I don't want to install a development version of
Oh, I'm working with the 13.X LTS :(
Great! Thanks! |
|
@qrilka sorry for taking so much time to respond. I had a huge backlog. I can confirm that #5042 fixes it! ❤️ Any ideas on what I could do to get this fix ASAP on a relatively stable |
Sorry, I should have been more clear. What I meant is that if I need to run a |
|
You could do that, sure. But that would be a substantial duplication in terms of disk space and CPU usage :) BTW the PRs were merged into |
It will use more disk sure, but that shouldn't be a problem. And it would be a temporary workaround.
Oh, that's good to know! I guess I could just give stable a try... |
|
I am going to close this issue given the passage of time and it appears to me from the comments that it may have been resolved. |
General summary/comments (optional)
stack hoogle commands failed due to not finding/installing hoogle
Steps to reproduce
Run any
stack hooglebased commandExpected
Either install hoogle then generate hoogle database or find hoogle then install database
Actual
$ stack --version
Version 2.1.1, Git revision f612ea8 (7648 commits) x86_64 hpack-0.31.2
curl -sSL https://get.haskellstack.org/ | sh
The text was updated successfully, but these errors were encountered: