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

base, bytestring, http2, time bounds #85

Merged
merged 1 commit into from
Mar 15, 2022

Conversation

avieth
Copy link
Contributor

@avieth avieth commented Mar 1, 2022

No description provided.

@ProofOfKeags
Copy link
Collaborator

What is the intended ghc build target here?

I tried with 9.2 since I think base 4.16.1 is used in 0.2 and it didn't work.

It seems to work with 9.0 though.

@avieth
Copy link
Contributor Author

avieth commented Mar 8, 2022

What is the intended ghc build target here?

9.2.1. I have it buliding, but I'm using nix with a custom overlay. What's the build failure you're seeing?

@ProofOfKeags
Copy link
Collaborator

fwiw I used 9.2.2 to test this build but here's what I got.

Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: http2-client-0.10.0.1 (user goal)
[__1] trying: tls-1.5.7 (dependency of http2-client)
[__2] trying: memory-0.16.0 (dependency of tls)
[__3] next goal: base (dependency of http2-client)
[__3] rejecting: base-4.16.1.0/installed-4.16.1.0 (conflict: memory =>
base<4.16)
[__3] skipping: base-4.16.0.0 (has the same characteristics that caused the
previous version to fail: excluded by constraint '<4.16' from 'memory')
[__3] rejecting: base-4.15.1.0, base-4.15.0.0, base-4.14.3.0, base-4.14.2.0,
base-4.14.1.0, base-4.14.0.0, base-4.13.0.0, base-4.12.0.0, base-4.11.1.0,
base-4.11.0.0, base-4.10.1.0, base-4.10.0.0, base-4.9.1.0, base-4.9.0.0,
base-4.8.2.0, base-4.8.1.0, base-4.8.0.0, base-4.7.0.2, base-4.7.0.1,
base-4.7.0.0, base-4.6.0.1, base-4.6.0.0, base-4.5.1.0, base-4.5.0.0,
base-4.4.1.0, base-4.4.0.0, base-4.3.1.0, base-4.3.0.0, base-4.2.0.2,
base-4.2.0.1, base-4.2.0.0, base-4.1.0.0, base-4.0.0.0, base-3.0.3.2,
base-3.0.3.1 (constraint from non-upgradeable package requires installed
instance)
[__3] fail (backjumping, conflict set: base, http2-client, memory)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: tls, base, http2-client, memory
Try running with --minimize-conflict-set to improve the error message.

@avieth
Copy link
Contributor Author

avieth commented Mar 9, 2022

Right, looks like nixpkgs applies the patch from this issue. Also this PR. Seems Vincent is MIA.

@avieth
Copy link
Contributor Author

avieth commented Mar 14, 2022

Never mind, he's done it! https://twitter.com/vincenthz/status/1502992810936762368

Should build with memory 0.17

@ProofOfKeags
Copy link
Collaborator

What command are you running and with what configs? I've never really used cabal directly (always used stack).

Do I need to specifically install [email protected]?

@avieth
Copy link
Contributor Author

avieth commented Mar 15, 2022

What command are you running and with what configs? I've never really used cabal directly (always used stack).

Do I need to specifically install [email protected]?

Should be enough to cabal update and then cabal v2-build.

@ProofOfKeags
Copy link
Collaborator

Can confirm that this seems to work. That said, I thought the v2-* commands were deprecated.

@ProofOfKeags ProofOfKeags merged commit 046b1f2 into haskell-grpc-native:master Mar 15, 2022
@avieth
Copy link
Contributor Author

avieth commented Mar 15, 2022

That said, I thought the v2-* commands were deprecated.

Oh I think you're right, and the old ones are opt-in by v1- prefix. I just use v2- by force of habit.

Well, not deprecated, but renamed to unprefixed.

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 this pull request may close these issues.

2 participants