-
Notifications
You must be signed in to change notification settings - Fork 240
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
withHoogle
does not respect exactDeps
for hoogle itself
#2277
Comments
There is upstream issue in hackage that breaks snoyberg/http-client#547 To workaround this issue you can override the
This will pin the |
thanks for the workaround tip with cabal picking whatever it likes still though this makes general reproducability more troublesome with cached results differing from uncached. Is there any scope for this being able to be pinned like exactDeps in the future? |
I don't think haskell.nix should be responsible for pinning tools like Haskell.nix has a source pin for Haskell.nix projects can pin
That should globally limit the Something else I should mention.
Currently there is no way to choose
|
Thanks for the info |
* Pin index-state used to build hoogle in tests See #2277 * Also fix shell-for test * Bump index-state to 2024-10-26
Describe the bug
we have a nix shell that looks very similar to the example
https://input-output-hk.github.io/haskell.nix/tutorials/development.html#how-to-get-a-development-shell
We use stackage for snapshots and currently target
nightly-2024-08-08
which importantly contains a working combination of data-default and http-client-tlshttps://www.stackage.org/nightly-2024-08-08/package/data-default-0.7.1.1
https://www.stackage.org/nightly-2024-08-08/package/http-client-tls-0.3.6.3
However if we enable
withHoogle: true
in the last few days we are unable to build this as it fails to compile with the combination ofhttp-client-tls-0.3.6.4
anddata-default-0.8.0
neither of which are in our snapshot.It seems that cabal itself is deciding which dependency versions to use which I was expecting
exactDeps
to stopExpected behavior
hoogle server should respect exactDeps or at least the snapshot
** Extra context **
This is the error you get currently when cabal picks the latest versions
The text was updated successfully, but these errors were encountered: