I thought this was in a snapshot, so I kept trying to run "stack install toodles" with

stack install: "Unknown package: toodles" about toodles HOT 20 CLOSED

aviaviavi commented on May 20, 2024

stack install: "Unknown package: toodles"

from toodles.

Comments (20)

aviaviavi commented on May 20, 2024

Thanks for opening! Hmm so you actually should not need to download the repo first... Did you try running stack update first?

from toodles.

aviaviavi commented on May 20, 2024

I can add stack update to the installation instructions if that was the issue

from toodles.

JeffreyBenjaminBrown commented on May 20, 2024

Aha! I'll try that on my computer at work soon.

But if that's the problem, it seems strange that the project's Stackage page would say "This package is not currently in any snapshots," no? Do snapshots not encompass the entire set of libraries that Stackage makes available?

from toodles.

aviaviavi commented on May 20, 2024

Yeah I see what you mean. Stack can install binaries from hackage just fine, so that's what's going on here. I should eventually get this into stackage proper as well

from toodles.

JeffreyBenjaminBrown commented on May 20, 2024

Good to know!

…

On Fri, Oct 26, 2018 at 10:56 AM Avi Press ***@***.***> wrote: Yeah I see what you mean. Stack can install binaries from hackage just fine, so that's what's going on here. I should eventually get this into stackage proper as well — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIfQTwliW26K1jEso03UsVzBRqdKO1OIks5uozCZgaJpZM4X8bCz> .

-- Jeff Brown | Jeffrey Benjamin Brown Website <https://msu.edu/~brown202/> | Facebook <https://www.facebook.com/mejeff.younotjeff> | LinkedIn <https://www.linkedin.com/in/jeffreybenjaminbrown>(spammy, so I often miss messages here) | Github <https://github.com/jeffreybenjaminbrown>

from toodles.

JeffreyBenjaminBrown commented on May 20, 2024

After running 'stack update' and without downloading the repo, I tried stack install toodles and got errors:

 
jeff@jeff-ThinkCentre-M700:~$ stack install toodles
Populated index cache.    

Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for toodles-0.1.0.12:
    aeson-1.2.4.0 from stack configuration does not match ==1.3.1.1 (latest matching
                  version is 1.3.1.1)
    blaze-html-0.9.0.1 from stack configuration does not match ==0.9.1.1 (latest matching
                       version is 0.9.1.1)
    directory-1.3.0.2 from stack configuration does not match ==1.3.1.5 (latest matching
                      version is 1.3.1.5)
    filepath-1.4.1.2 from stack configuration does not match ==1.4.2 (latest matching
                     version is 1.4.2)
    http-types-0.9.1 from stack configuration does not match ==0.12.2 (latest matching
                     version is 0.12.2)
    megaparsec-6.3.0 from stack configuration does not match ==6.5.0 (latest matching
                     version is 6.5.0)
    servant-0.11 from stack configuration does not match ==0.14.1 (latest matching version
                 is 0.14.1)
    servant-blaze-0.7.1 from stack configuration does not match ==0.8 (latest matching
                        version is 0.8)
    servant-server-0.11.0.1 from stack configuration does not match ==0.14.1 (latest
                            matching version is 0.14.1)
    text-1.2.2.2 from stack configuration does not match ==1.2.3.1 (latest matching
                 version is 1.2.3.1)
    transformers-0.5.2.0 from stack configuration does not match ==0.5.5.0 (latest
                         matching version is 0.5.5.0)
    wai-3.2.1.1 from stack configuration does not match ==3.2.1.2 (latest matching version
                is 3.2.1.2)
    warp-3.2.13 from stack configuration does not match ==3.2.25 (latest matching version
                is 3.2.25)
    yaml-0.8.28 from stack configuration does not match ==0.8.32 (latest matching version
                is 0.8.32)
needed since toodles is a build target.

Some potential ways to resolve this:

  * Recommended action: try adding the following to your extra-deps
    in /home/jeff/.stack/global-project/stack.yaml:

- aeson-1.3.1.1
- blaze-html-0.9.1.1
- directory-1.3.1.5
- filepath-1.4.2
- http-types-0.12.2
- megaparsec-6.5.0
- servant-0.14.1
- servant-blaze-0.8
- servant-server-0.14.1
- text-1.2.3.1
- transformers-0.5.5.0
- wai-3.2.1.2
- warp-3.2.25
- yaml-0.8.32

  * Set 'allow-newer: true' to ignore all version constraints and build anyway.

  * You may also want to try using the 'stack solver' command.

Plan construction failed.

from toodles.

aviaviavi commented on May 20, 2024

Hmm interesting... Would you mind telling me the output when you run:

grep resolver ~/.stack/global-project/stack.yaml

from toodles.

aviaviavi commented on May 20, 2024

My current guess is that maybe your global stack is on a resolver that's too old. If that's the case, I should update the docs to call that out

from toodles.

JeffreyBenjaminBrown commented on May 20, 2024

That looks like it was the problem. I was using resolver: lts-10.5. I edited ~/.stack/global-project/stack.yaml to include instead the line resolver: lts-12.14 (that's the lts I see when I google "latest stack snapshot"), and now stack install toodles has caused (so far) about five minutes of work to happen, with no reported errors so far.

from toodles.

JeffreyBenjaminBrown commented on May 20, 2024

Nope. This time it couldn't find the cabal files for the snapshot. It asked me to try again, which I did, resulting in the same error. My next strategy is to see if I needed to have cabal installed.

e
jeff@jeff-ThinkCentre-M700:~$ stack install toodles
Downloaded lts-12.14 build plan.    
Preparing to install GHC (nopie) to an isolated location.
This will not interfere with any system-level installation.
Downloaded ghc-nopie-8.4.3.                                      
Installed GHC.                                                                      
Unable to load cabal files for snapshot

----
Deleting cached snapshot file: /home/jeff/.stack/build-plan/lts-12.14.yaml
Recommendation: try running again. If this fails again, open an upstream issue at:
https://github.com/fpco/lts-haskell/issues/new
----

Unable to parse cabal file for bhoogle-0.1.3.5@sha256:a3393794b22faabeb564c57f4a9506390b6b97b9792c6b4e130f15bf116099fd,1806: NoParse "license" 7
jeff@jeff-ThinkCentre-M700:~$ stack install toodles
Unable to load cabal files for snapshot

----
Deleting cached snapshot file: /home/jeff/.stack/build-plan/lts-12.14.yaml
Recommendation: try running again. If this fails again, open an upstream issue at:
https://github.com/fpco/lts-haskell/issues/new
----

Unable to parse cabal file for bhoogle-0.1.3.5@sha256:a3393794b22faabeb564c57f4a9506390b6b97b9792c6b4e130f15bf116099fd,1806: NoParse "license" 7
jeff@jeff-ThinkCentre-M700:~$ cabal update

from toodles.

JeffreyBenjaminBrown commented on May 20, 2024

Nope, that didn't do it either; I'm getting the same error (identical -- I ran a diff to test):

jeff@jeff-ThinkCentre-M700:~$ stack install toodles         
Unable to load cabal files for snapshot

----
Deleting cached snapshot file: /home/jeff/.stack/build-plan/lts-12.14.yaml
Recommendation: try running again. If this fails again, open an upstream issue at:
https://github.com/fpco/lts-haskell/issues/new
----

Unable to parse cabal file for bhoogle-0.1.3.5@sha256:a3393794b22faabeb564c57f4a9506390b6b97b9792c6b4e130f15bf116099fd,1806: NoParse "license" 7

from toodles.

aviaviavi commented on May 20, 2024

hmm hoogle erroring is strange, there's no toodles dependency on hoogle.

assuming you didn't do this already, does a stack update after you revised your global resolver affect it?

from toodles.

JeffreyBenjaminBrown commented on May 20, 2024

Nope, same error.

from toodles.

aviaviavi commented on May 20, 2024

This is strange, I'm completely unable to reproduce that. If my global resolver is at 12.14, it installs for me on both mac and linux. But the fact that you're getting an error while building bhoogle seems unrelated to toodles so I'm not sure where that leaves us. Is it possible you need a stack clean? (I've never actually needed that command so that's a bit of a shot in the dark)

by the way I really appreciate you bearing with me to work through this :)

from toodles.

JeffreyBenjaminBrown commented on May 20, 2024

And I appreciate toodles!

stack clean generates the error, which suggests this is not a toodles-specific problem:

jeff@jeff-ThinkCentre-M700:~$ stack clean
Unable to load cabal files for snapshot

----
Deleting cached snapshot file: /home/jeff/.stack/build-plan/lts-12.14.yaml
Recommendation: try running again. If this fails again, open an upstream issue at:
https://github.com/fpco/lts-haskell/issues/new
----

Unable to parse cabal file for bhoogle-0.1.3.5@sha256:a3393794b22faabeb564c57f4a9506390b6b97b9792c6b4e130f15bf116099fd,1806: NoParse "license" 7

from toodles.

aviaviavi commented on May 20, 2024

Ah! commercialhaskell/lts-haskell#164

try stack upgrade

from toodles.

damiencourousse commented on May 20, 2024

What is your version of stack? I experienced the same problem sometimes ago. You may need to upgrade stack, either with your package manager or with ‘stack upgrade’.

…

Le 26 oct. 2018 à 23:57, Jeffrey Benjamin Brown ***@***.***> a écrit : Nope, that didn't do it either; I'm getting the same error (identical -- I ran a diff to test): . ***@***.***:~$ stack install toodles Unable to load cabal files for snapshot ---- Deleting cached snapshot file: /home/jeff/.stack/build-plan/lts-12.14.yaml Recommendation: try running again. If this fails again, open an upstream issue at: https://github.com/fpco/lts-haskell/issues/new ---- Unable to parse cabal file for ***@***.***:a3393794b22faabeb564c57f4a9506390b6b97b9792c6b4e130f15bf116099fd,1806: NoParse "license" 7 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

from toodles.

damiencourousse commented on May 20, 2024

Sorry, Avi, I did not see your answer. Best,

…

Le 27 oct. 2018 à 00:34, Avi Press ***@***.***> a écrit : Ah! commercialhaskell/lts-haskell#164 try stack upgrade — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

from toodles.

JeffreyBenjaminBrown commented on May 20, 2024

Sorry, meant to reply to this! stack upgrade did the trick. (I can't say what version it was at before upgrading until Monday when I'm at work again. Actually maybe even then -- now that I've upgraded, will there be a record of what the earlier version was?) Thanks!

…

On Sat, Oct 27, 2018 at 3:40 AM Damien Couroussé ***@***.***> wrote: Sorry, Avi, I did not see your answer. Best, > Le 27 oct. 2018 à 00:34, Avi Press ***@***.***> a écrit : > > Ah! commercialhaskell/lts-haskell#164 > > try stack upgrade > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIfQT3VHzGDSAEqIH-0VI0vpyBszq_L4ks5upBv7gaJpZM4X8bCz> .

from toodles.

aviaviavi commented on May 20, 2024

I'm not sure actually, but glad to hear that did the trick! I'll close this for now but we can always reopen if anyone else has similar installation issues

from toodles.

stack install: "Unknown package: toodles" about toodles HOT 20 CLOSED

Comments (20)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent