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

Bump binary upper version bounds #15

Merged
merged 1 commit into from Jul 31, 2016

Conversation

Projects
None yet
3 participants
@RyanGlScott
Member

RyanGlScott commented Jul 29, 2016

ghc-events is currently excluded from Stackage due to its restrictive upper version bounds on binary, as GHC 8.0.1 is shipped with binary-0.8.3.0.

@Mikolaj Mikolaj merged commit 1a4498b into haskell:master Jul 31, 2016

@Mikolaj

This comment has been minimized.

Show comment
Hide comment
@Mikolaj

Mikolaj Jul 31, 2016

Member

Thank you for the PR. Merged to master. Do we need to tag a release or upload to Hackage now or anything else, to make Stackage happy?

Member

Mikolaj commented Jul 31, 2016

Thank you for the PR. Merged to master. Do we need to tag a release or upload to Hackage now or anything else, to make Stackage happy?

@RyanGlScott

This comment has been minimized.

Show comment
Hide comment
@RyanGlScott

RyanGlScott Jul 31, 2016

Member

The most recent version on Hackage would need to have its upper version bounds on binary lifted. Whether you wish to do this via a new release or by editing the current release's metadata is up to you.

Member

RyanGlScott commented Jul 31, 2016

The most recent version on Hackage would need to have its upper version bounds on binary lifted. Whether you wish to do this via a new release or by editing the current release's metadata is up to you.

@Mikolaj

This comment has been minimized.

Show comment
Hide comment
@Mikolaj

Mikolaj Jul 31, 2016

Member

@kvelicka: would you make the call?

Member

Mikolaj commented Jul 31, 2016

@kvelicka: would you make the call?

@kvelicka

This comment has been minimized.

Show comment
Hide comment
@kvelicka

kvelicka Aug 1, 2016

Collaborator

I think that editing the current release's metadata would be the better choice at this point. There is still work to be done to get 0.5 to a release-worthy state and I will only be able to contribute to it later on - currently moving cities, starting a new job etc.

Collaborator

kvelicka commented Aug 1, 2016

I think that editing the current release's metadata would be the better choice at this point. There is still work to be done to get 0.5 to a release-worthy state and I will only be able to contribute to it later on - currently moving cities, starting a new job etc.

@Mikolaj

This comment has been minimized.

Show comment
Hide comment
@Mikolaj

Mikolaj Aug 1, 2016

Member

So be it. :) @RyanGlScott: would you be so kind? Thank you!

Member

Mikolaj commented Aug 1, 2016

So be it. :) @RyanGlScott: would you be so kind? Thank you!

@RyanGlScott

This comment has been minimized.

Show comment
Hide comment
@RyanGlScott

RyanGlScott Aug 1, 2016

Member

I'm not a Hackage trustee, so I don't have the power to do that. You should be able to edit the metadata yourself by going to the Hackage page for ghc-events and clicking "edit package information".

Member

RyanGlScott commented Aug 1, 2016

I'm not a Hackage trustee, so I don't have the power to do that. You should be able to edit the metadata yourself by going to the Hackage page for ghc-events and clicking "edit package information".

@Mikolaj

This comment has been minimized.

Show comment
Hide comment
@Mikolaj

Mikolaj Aug 1, 2016

Member

Oh, you are right. I've done it right now. Please verify. Thank you again!

Member

Mikolaj commented Aug 1, 2016

Oh, you are right. I've done it right now. Please verify. Thank you again!

@RyanGlScott

This comment has been minimized.

Show comment
Hide comment
@RyanGlScott

RyanGlScott Aug 2, 2016

Member

It works! ghc-events is now back in Stackage nightly.

Member

RyanGlScott commented Aug 2, 2016

It works! ghc-events is now back in Stackage nightly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment