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

Add servant back to stackage #1340

Closed
arianvp opened this issue Sep 24, 2020 · 7 comments · Fixed by commercialhaskell/stackage#5721
Closed

Add servant back to stackage #1340

arianvp opened this issue Sep 24, 2020 · 7 comments · Fixed by commercialhaskell/stackage#5721

Comments

@arianvp
Copy link
Member

arianvp commented Sep 24, 2020

https://github.com/commercialhaskell/stackage/blob/master/build-constraints.yaml#L1540

Now that everything builds with GHC 8.10 #1331 #1295 we should be able to re-add ourselves.

I do not know who controls that current mailing list that's in build-constraints. If the answer is that nobody does anymore than we should update it

@arianvp
Copy link
Member Author

arianvp commented Sep 24, 2020

Probably needs #1334 too

@arianvp
Copy link
Member Author

arianvp commented Oct 12, 2020

I asked around about the mailing list; but nobody responded. I suggest we create a new email address with the new maintainers; instead of trying to get hold of ownership of the old one.

@domenkozar
Copy link
Contributor

@arianvp
Copy link
Member Author

arianvp commented Oct 12, 2020

Nice it seems a bit simpler than the haskell-ci stuff; which only seems to work with travis. I'll have a look

@domenkozar
Copy link
Contributor

Yeah I find having CI abstraction in a releasable haskell package quite a feedback killer.

@serras
Copy link
Contributor

serras commented Oct 12, 2020

I think with #1348 merged, you can now try to add it again to Stackage.

@maksbotan
Copy link
Contributor

Done! Core packages, servant-blaze, servant-multipart and servant-swagger-ui are in nightly now: https://www.stackage.org/diff/nightly-2020-11-06/nightly-2020-11-08

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.

4 participants