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.

Sign up for GitHub

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

Jump to bottom

aeson 1.1.0.0 #2177

Closed
7 tasks
decentral1se opened this issue Jan 2, 2017 · 25 comments · Fixed by klappvisor/haskell-telegram-api#86
Closed
7 tasks

aeson 1.1.0.0 #2177

decentral1se opened this issue Jan 2, 2017 · 25 comments · Fixed by klappvisor/haskell-telegram-api#86
Labels
failure: bounds

Comments

@decentral1se
Copy link
Member

decentral1se commented Jan 2, 2017 •
edited
Loading

Following from haskell/aeson#503.

aeson-1.1.0.0 (Adam Bergmark adam@bergmark.nl @bergmark) is out of bounds for:

Updated: February 1rst, 2017
tfausak added a commit to tfausak/github-release that referenced this issue Jan 2, 2017
@tfausak
Allow aeson 1.1
074a5d7 
commercialhaskell/stackage#2177
tfausak added a commit to tfausak/octane that referenced this issue Jan 2, 2017
@tfausak
Allow aeson 1.1
791532d 
commercialhaskell/stackage#2177
tfausak added a commit to tfausak/rattletrap that referenced this issue Jan 2, 2017
@tfausak
Allow aeson 1.1
d80133c 
commercialhaskell/stackage#2177
decentral1se added a commit that referenced this issue Jan 2, 2017
@decentral1se
Upper bounds for #2177 and #2178.
d56fd19
tfausak added a commit to tfausak/ratel that referenced this issue Jan 2, 2017
@tfausak
Allow aeson 1.1
27cd4fb 
commercialhaskell/stackage#2177
tfausak added a commit to tfausak/strive that referenced this issue Jan 2, 2017
@tfausak
Allow aeson 1.1
a59d6b0 
commercialhaskell/stackage#2177
@hadronized
Copy link
Contributor

smoothie fixed.

@fosskers
Copy link
Contributor

fosskers commented Jan 2, 2017

microlens-aeson fixed.

adinapoli added a commit to adinapoli/mandrill that referenced this issue Jan 2, 2017
@adinapoli
Relax Aeson upper bound (see commercialhaskell/stackage/issues/2177 )
a1d9573
adinapoli added a commit to adinapoli/mandrill that referenced this issue Jan 2, 2017
@adinapoli
Merge pull request #42 from adinapoli/v0.5.3.1
3d8dc75 
Relax Aeson upper bound (see commercialhaskell/stackage/issues/2177 )
@mrkkrp
Copy link
Contributor

mrkkrp commented Jan 2, 2017

req, slug, and stache should be OK now.

@bitemyapp bitemyapp mentioned this issue Jan 2, 2017
Closed
@WillSewell
Copy link
Contributor

pusher-http-haskell fixed.

@wereHamster
Copy link
Contributor

I suspect that avers is compatible and only requires a dependency bounds bump. But I can't be sure, I can't actually buildavers because it depends on servant and a version that is compatible with aeson-1.1 has not been released yet.

Will there be enough time between servant releasing a version I can test against and stackage bumping the bounds of aeson, or should I simply bump the upper bounds and hope everything continues to work?

@jsantos17 jsantos17 mentioned this issue Jan 3, 2017
Closed
@bergmark
Copy link
Member

bergmark commented Jan 3, 2017

@wereHamster did you try building avers+servant with allow-newer in cabal-install/stack? If that works you can safely bump it. But in general we should try to improve the process so we don't disable packages that haven't gotten a notification.

@wereHamster
Copy link
Contributor

@bergmark yes, that worked. Though I was confused at first because stack didn't recognize that option on the commandline, neither stack --allow-newer build nor stack build --allow-newer worked. I had to put the option into stack.yaml.

The upper bound is already adjusted on hackage.

@ghost
Copy link

ghost commented Jan 3, 2017

twitter-feed fixed.

@MichelBoucey
Copy link
Contributor

cayley-client, glabrous fixed.

@alpmestan alpmestan mentioned this issue Jan 7, 2017
Closed
@killy971
Copy link
Contributor

hpc-coveralls fixed.

@killy971 killy971 mentioned this issue Jan 10, 2017
Closed
@MichaelXavier
Copy link
Contributor

ua-parser fixed. Working on bloodhound which should fix katip and katip-elasticsearch.

@MichaelXavier
Copy link
Contributor

bloodhound-0.12.1.0 works now, and thus katip-0.3.1.4 and katip-elasticsearch-0.3.0.2.

@codedmart
Copy link
Contributor

rethinkdb-2.2.0.8 works

@cdepillabout
Copy link
Member

Waiting on PR to be merged for hailgun:
https://bitbucket.org/robertmassaioli/hailgun/pull-requests/19/bump-aeson-version/diff

@christiaanb
Copy link
Contributor

Fixed in clash-lib-0.7

@YoEight
Copy link
Contributor

YoEight commented Jan 22, 2017

Fixed in eventstore-0.14.0.1

@stepcut
Copy link
Contributor

stepcut commented Jan 29, 2017

Fixed clckwrks, clckwrks-plugin-page, userid, and happstack-authenicate.

@bergmark bergmark changed the title aeson1.1 aeson 1.1.0.0 Jan 30, 2017
@MichelBoucey
Copy link
Contributor

Fixed in cayley-client-0.4.0

@nboldi
Copy link
Contributor

nboldi commented Jan 31, 2017

Fixed for haskell-tools-*-0.5

@freizl
Copy link
Contributor

freizl commented Feb 1, 2017

Fixed for hoauth2-0.5.8

bergmark added a commit that referenced this issue Feb 1, 2017
@bergmark
hoauth2 upper bound for #2177
209fffd
@NCrashed
Copy link
Contributor

NCrashed commented Feb 1, 2017

Fixed for aeson-injector-1.0.7.0

@phadej
Copy link
Contributor

phadej commented Feb 4, 2017

servant-swagger and servant-swagger-ui updated

@DanBurton
Copy link
Contributor

DanBurton commented Feb 10, 2017 •
edited by decentral1se
Loading

LTS 8 will be released soon, probably with aeson-1.0.2.1.

After the LTS 8.0 release, the packages listed below (and any that depend on them) will continue to be included in LTS 8 builds, but will be dropped from nightly builds until a release compatible with aeson-1.1.0.0 is made available.

aeson-1.1.0.0 (Adam Bergmark adam@bergmark.nl @bergmark) is out of bounds for:

@cdepillabout
Copy link
Member

hailgun currently has support for aeson-1.1, it just needs a release to Hackage. I gave the maintainer a little nudge here:

https://bitbucket.org/robertmassaioli/hailgun/pull-requests/19/bump-aeson-version/diff#comment-31241115

This was referenced Feb 10, 2017
Merged
Closed
Merged
@WillSewell
Copy link
Contributor

opaleye fixed.

@WillSewell WillSewell mentioned this issue Feb 12, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failure: bounds
Projects
None yet
Milestone
No milestone