Cabal file info not found for floskell-0.10.4

[sir4ur0n]

This problem is surprising, but whenever I run a stack command (build, clean, etc.), I get this error:

Cabal file info not found for floskell-0.10.4, updating
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
Downloading timestamp
No package index update available and cache up to date
Package index cache populated
Could not find floskell-0.10.4 on Hackage
Possible candidates: floskell-0.10.0@sha256:442dd0f7d01b06d628c361628d566b9466b3edc7a23b11694c1496ddfd4ac5ae,4350, floskell-0.10.1@sha256:dd9a3e0ac90d672135c6911474213da5f29b05780ef1058fcff7330090b587c9,4350, floskell-0.10.2@sha256:5d0c4988a8f9d1cd0e22604751356cfa69319dc518ad30ec1bda0e07c9a78d86,4471, floskell-0.10.3@sha256:43ac46830200712934cfd942eafc7285b5f61dbd7a7740a90917fa08a4c7cb2b,4512.

This is all the more surprising as I do see floskell-0.10.4 on Hackage

Maybe this is a bug in FpComplete mirror? Has anybody else the same issue?

Note: even if I changed the floskell version in stack.yaml to 0.10.3, I then get a similar issue with fourmolu:

Cabal file info not found for fourmolu-0.1.0.0@rev:1, updating
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
Downloading timestamp
No package index update available and cache up to date
Package index cache populated
Could not find fourmolu-0.1.0.0@rev:1 on Hackage
The specified revision was not found.
Possible candidates: fourmolu-0.1.0.0@sha256:f57ba1d7f0c8b7009259b428fd66264ea18ac2b714d60b6c760bd8faab846b73,6204.

I have already tried running cabal update and stack update but to no avail...

[jneira]

I assume you are using the default project stack.yaml which uses lts-14.27/ghc-8.6.5. Are you using nix?

[jneira]

It turns out that the default stack.yaml was failing for me with

PS D:\dev\ws\haskell\hls> stack build

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

In the dependencies for HsYAML-aeson-0.2.0.0:
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed due to haskell-language-server-0.3.0.0 -> HsYAML-aeson-0.2.0.0

Dependency cycle detected in packages:
    [aeson,these,aeson,ghcide]

In the dependencies for aeson-pretty-0.8.8:
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed due to ghcide-0.2.0 -> aeson-pretty-0.8.8

In the dependencies for brittany-0.12.1.1:
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed due to haskell-language-server-0.3.0.0 -> brittany-0.12.1.1

In the dependencies for floskell-0.10.4:
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed due to haskell-language-server-0.3.0.0 -> floskell-0.10.4

In the dependencies for fourmolu-0.1.0.0:
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed due to haskell-language-server-0.3.0.0 -> fourmolu-0.1.0.0

In the dependencies for haskell-language-server-0.3.0.0(+pedantic):
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed since haskell-language-server is a build target.

In the dependencies for haskell-lsp-0.22.0.0:
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed due to ghcide-0.2.0 -> haskell-lsp-0.22.0.0

In the dependencies for haskell-lsp-types-0.22.0.0:
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed due to ghcide-0.2.0 -> haskell-lsp-types-0.22.0.0

In the dependencies for hie-bios-0.6.1:
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed due to ghcide-0.2.0 -> hie-bios-0.6.1

In the dependencies for lsp-test-0.11.0.4:
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed due to ghcide-0.2.0 -> lsp-test-0.11.0.4

In the dependencies for stylish-haskell-0.11.0.3:
    aeson dependency cycle detected: aeson, these, aeson, ghcide
needed due to haskell-language-server-0.3.0.0 -> stylish-haskell-0.11.0.3
In the dependencies for these-1.0.1:
    aeson dependency cycle detected: aeson, these, aeson, ghcide

In the dependencies for yaml-0.11.2.0:

Some different approaches to resolving this:

Plan construction failed.

The slightly different stack-8.6.5.yaml works though so i am gonna open a pr to copy the latter onto the former.
Not sure it it is related with your issue, could you try stack-8.6.5.yamljust in case?

[sir4ur0n]

I assume you are using the default project stack.yaml which uses lts-14.27/ghc-8.6.5. Are you using nix?

Yes and yes 😁

After manually fixing a few dependency versions in stack.yaml I got the exact same issue of cyclic dependency, I'll take a look at your PR

[jneira]

Afaiu we can close this one, @sir4ur0n feel free to reopen it though