Skip to content
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

Support hashable-1.4? #394

Closed
kindaro opened this issue Dec 12, 2021 · 3 comments · Fixed by #399
Closed

Support hashable-1.4? #394

kindaro opened this issue Dec 12, 2021 · 3 comments · Fixed by #399

Comments

@kindaro
Copy link

kindaro commented Dec 12, 2021

Currently, the bounds for hashable look like this: hashable (>=1.2 && <1.4). But hashable-1.4 already has two minor versions. Maybe the upper bound can be raised to include them?

@Anton-Latukha
Copy link

Anton-Latukha commented Jan 6, 2022

This broke the downstream project CI:

[__2] skipping: hashable-1.4.0.1, hashable-1.4.0.0 (has the same
characteristics that caused the previous version to fail: excluded by
constraint '>=1.2 && <1.4' from 'relude')
[__2] trying: hashable-1.3.5.0
[__3] next goal: base (dependency of hnix)
[__3] rejecting: base-4.15.1.0/installed-4.15.1.0 (conflict: hashable =>
ghc-bignum>=1.0 && <1.1 || >=1.2 && <1.3, base =>
ghc-bignum==1.1/installed-1.1)

So ghc-bignum on Hackage has only 1.0, 1.2 releases, while 1.1 is a boot library in GHC 9.0.
And the v2-freeze or v2-test do not allow --allow-newer to circumvent this.

To solve this downstream the downstream project/CI workflows would need to be redesigned to have .project to freeze on some Hackage index-state to circumvent this & pretend to live in the old Hackage state & which would imply updating index-state all the time on any update to deps.

@Anton-Latukha
Copy link

Anton-Latukha commented Jan 6, 2022

Sidenote: Upload of ghc-bignum 1.1 was requested at https://gitlab.haskell.org/ghc/ghc/-/issues/19632#note_400751.

@Anton-Latukha
Copy link

Several things happened in upstream packages to solve this, seems like upstream things should be resolved now.

relude can upgrade to new hashable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants