Stackage: aeson 0.11

[bergmark]

Please see the changelog. Most likely your package will be fine without any changes but there are subtle semantic changes from 0.10.

Please let us (stackage curators and aeson maintainers) know if there are any issues with this upgrade as soon as possible. For the 0.10 release the maintainer was unresponsive, we didn't consistently poke stackage maintainers enough, and a lot of issues didn't show up until months later. I hope we can do better on all three fronts this time!

Here is some info on building nightly against aeson 0.11: https://github.com/bos/aeson/issues/355

aeson-0.11.0.0 is out of bounds for:

• [x] aeson-compat-0.3.0.0 (>=0.7.0.6 && < 0.11). Oleg Grenrus oleg.[email protected] @phadej. @phadej
• [x] aeson-extra-0.3.1.0 (>=0.7.0.6 && < 0.11). Oleg Grenrus oleg.[email protected] @phadej. @phadej
• [x] aeson-utils-0.3.0.2 (>=0.6 && < 0.11). Silk [email protected]. @bergmark @hesselink
• [x] arbtt-0.9.0.7 (>=0.6 && < 0.11). Joachim Breitner [email protected].
• [x] binary-orphans-0.1.4.0 (>=0.7.0.6 && < 0.10.1). Oleg Grenrus oleg.[email protected] @phadej. @phadej
• [x] binary-tagged-0.1.3.0 (>=0.8 && < 0.11). Oleg Grenrus oleg.[email protected] @phadej. @phadej
• [x] clckwrks-0.23.13 (>=0.5 && < 0.11). Jeremy Shaw [email protected] @stepcut. @stepcut
• [x] clckwrks-plugin-page-0.4.3 (>=0.6 && < 0.11). Jeremy Shaw [email protected] @stepcut. @stepcut
• [ ] datadog-0.1.0.1 (>=0.8 && < 0.10). Ian Duncan [email protected] @iand675. @iand675
• [x] digestive-functors-aeson-1.1.18 (>=0.7 && < 0.11). Oliver Charles [email protected]. @ocharles
• [x] dixi-0.6.0.5 (>=0.8 && < 0.11). Liam O'Connor [email protected]. @liamoc
• [x] ekg-0.4.0.8 (< 0.11). Luke Iannini [email protected] @lukexi. @tibbe
• [x] ekg-json-0.1.0.0 (< 0.11). Yann Esposito yann.[email protected]. @tibbe
• [x] elm-bridge-0.2.1.0 (==0.9.*). Alexander Thiemann [email protected]. @agrafix
• [x] engine-io-1.2.12 (>=0.7 && < 0.11). Oliver Charles [email protected]. @ocharles
• [x] eventstore-0.10.0.1 (>=0.8 && < 0.11). Yorick Laupa yo.[email protected] @YoEight. @YoEight
• [x] fay-0.23.1.12 (>0.6 && < 0.11). Adam Bergmark [email protected]. @bergmark
• [ ] flowdock-0.3.0.1 (>=0.8 && < 0.10). Ian Duncan [email protected] @iand675. @brewtown
• [x] generic-aeson-0.2.0.7 (>=0.6 && < 0.11). Silk [email protected]. @bergmark @hesselink
• [x] gipeda-0.2 (>=0.7 && < 0.11). Joachim Breitner [email protected]. @nomeata
• [x] github-0.14.1 (>=0.7.0.6 && < 0.11). Oleg Grenrus oleg.[email protected] @phadej. @phadej
• [x] happstack-authenticate-2.3.3 (>=0.4 && < 0.11). Jeremy Shaw [email protected] @stepcut. @stepcut
• [x] haxl-0.3.1.0 (>=0.6 && < 0.11). Oleg Grenrus oleg.[email protected] @phadej. @facebook
• [x] heist-0.14.1.1 (>=0.6 && < 0.11). No maintainer. @mightybyte
• [x] hoauth2-0.5.2 (>=0.9 && < 0.11). Haisheng Wu [email protected]. @freizl
• [x] hpc-coveralls-1.0.3 (>=0.7.1 && < 0.11). Michael Snoyman [email protected] @snoyberg. @guillaume-nargeot
• [x] ide-backend-0.10.0.1 (>=0.6.2 && < 0.11). FP Complete [email protected] @snoyberg.
• [x] ide-backend-common-0.10.1.2 (>=0.6.2 && < 0.11). No maintainer.
• [x] ihaskell-0.8.3.0 (>=0.7 && < 0.11). Andrew Gibiansky andrew.[email protected] @gibiansky. @gibiansky
• [x] ipython-kernel-0.8.3.0 (>=0.6 && < 0.11). Andrew Gibiansky andrew.[email protected] @gibiansky. @gibiansky
• [x] json-autotype-1.0.10 (>=0.7 && < 0.11). Michal J. Gajda [email protected]. @mgajda
• [x] json-schema-0.7.4.1 (>=0.7 && < 0.11). Silk [email protected]. @bergmark @hesselink
• [x] lens-aeson-1.0.0.5 (>=0.7.0.5 && < 0.11). Edward Kmett [email protected]. @lens
• [x] mandrill-0.5.0.0 (>=0.7.0.3 && < 0.11.0.0). Alfredo Di Napoli alfredo.[email protected]. @adinapoli
• [x] microlens-aeson-2.1.0 (>=0.7.0.5 && < 0.11). Colin Woodbury [email protected] @fosskers. @fosskers
• [x] opaleye-0.4.2.0 (>=0.6 && < 0.11). Tom Ellis [email protected]. @tomjaguarpaw
• [x] pagerduty-0.0.4 (>=0.8 && < 0.10). Brendan Hay brendan.g.[email protected] @brendanhay. @brendanhay
• [x] pandoc-1.16.0.2 (>=0.7.0.5 && < 0.11). No maintainer. @jgm
• [x] pandoc-citeproc-0.9 (>=0.7 && < 0.11). No maintainer. @jgm
• [x] pandoc-types-1.16.0.1 (>=0.6.2 && < 0.11). No maintainer. @jgm
• [x] persistent-template-2.1.5 (>=0.7 && < 0.11). Michael Snoyman [email protected] @snoyberg. @snoyberg
• [x] pipes-aeson-0.4.1.5 (>=0.6.1 && < 0.11). Renzo Carbonara [email protected] @k0001. @k0001
• [x] profiteur-0.3.0.1 (>=0.6 && < 0.11). Jasper Van der Jeugt. @jaspervdj
• [x] purescript-0.8.0.0 (>=0.8 && < 0.11). Oleg Grenrus oleg.[email protected] @phadej. @purescript
• [x] pusher-http-haskell-0.3.0.1 (>=0.8 && < 0.11). Will Sewell [email protected] @willsewell. @pusher-community
• [x] rest-core-0.38 (>=0.7 && < 0.11). Silk [email protected]. @bergmark @hesselink
• [x] rest-gen-0.19.0.2 (>=0.7 && < 0.11). Silk [email protected]. @bergmark @hesselink
• [x] rest-stringmap-0.2.0.6 (>=0.7 && < 0.11). Silk [email protected].
• [x] rest-types-1.14.0.1 (>=0.7 && < 0.11). Silk [email protected]. @bergmark @hesselink
• [x] rethinkdb-2.2.0.2 (>=0.7 && < 0.11). Brandon Martin [email protected] @codedmart. @atnnn
• [x] riak-0.9.1.1 (>=0.8 && < 0.11). Tim McGilchrist [email protected] @tmcgilchrist. @markhibberd
• [x] servant-server-0.4.4.6 (>=0.7 && < 0.11). Haskell Servant [email protected] @jkarni. @haskell-servant
• [x] servant-yaml-0.1.0.0 (>=0.8.0.2 && < 0.11). Oleg Grenrus oleg.[email protected] @phadej. @phadej
• [x] smoothie-0.4.2.1 (>=0.8 && < 0.11). Dimitri Sabadie [email protected]. @phaazon
• [x] snap-0.14.0.6 (==0.6.* || >=0.7.0.4 && < 0.11). No maintainer. @mightybyte
• [x] snaplet-fay-0.3.3.13 (>=0.6 && < 0.11). Adam Bergmark [email protected]. @bergmark
• [x] socket-io-1.3.4 (>=0.7 && < 0.11). Oliver Charles [email protected]. @ocharles
• [x] stack-1.0.2 (>=0.8.0.2 && < 0.11). Emanuel Borsboom [email protected] @borsboom. @commercialhaskell
• [x] stripe-core-2.0.2 (>=0.8 && < 0.10). David Johnson djohnson.[email protected] @dmjio. @dmjio
• [x] stripe-http-streams-2.0.2 (>=0.8 && < 0.10). David Johnson djohnson.[email protected] @dmjio. @dmjio
• [x] stylish-haskell-0.5.15.1 (>=0.6 && < 0.11). Jasper Van der Jeugt. @jaspervdj
• [x] tttool-1.6 (>=0.7 && < 0.11). Joachim Breitner [email protected]. @entropia
• [x] twitter-feed-0.2.0.4 (>=0.8 && < 0.11). Stack Builders [email protected] @stackbuilders. @CristhianMotoche @jpvillaisaza @jsantos17 @jsl @sestrella
• [x] userid-0.1.2.3 (>=0.8 && < 0.11). Jeremy Shaw [email protected] @stepcut. @stepcut
• [x] wai-routes-0.9.6 (>=0.8 && < 0.11). Anupam Jain [email protected]. @ajnsit
• [x] webdriver-0.8.1 (>=0.6.2.0 && < 0.11). Adam Curtis kallisti.[email protected] @kallisti-dev. @kallisti-dev
• [x] yesod-auth-oauth2-0.1.6 (>=0.6 && < 0.11). Paul Harper [email protected]. @thoughtbot

[YoEight]

eventstore has been updated and uploaded on Hackage

[adinapoli]

Mandrill 0.5.1.0 is on Hackage.

[bergmark]

A reminder that when there are lots of packages pending like here there's no need to comment on individual updated packages as it doesn't affect our workflow. No sweat :)

[adinapoli]

@bergmark I guessed that, sorry! It would be quite handy for us to be able to toggle somehow the checkboxes generated automatically, once the relevant packages we maintain are patched, but apparently we lack the permission to do so. That might cut comment traffic quite a bit! :wink:

[phaazon]

I’ve never been told about that .:!. I need to inquire a little bit deeper before pushing a support fix. :)

[bergmark]

I should also note this list of packages that have known build failures:

• [x] aeson-extra - Oleg Grenrus oleg.[email protected] @phadej
• [x] aeson-compat - Oleg Grenrus oleg.[email protected] @phadej
• [ ] ndjson-conduit - Sam Rijs [email protected] @srijs
• [x] argon - Michele Lacchia [email protected] @rubik
• [x] haskell-neo4j-client - Antoni Silvestre antoni.[email protected] @asilvestre
• [ ] mangopay - Felipe Lessa felipe.[email protected] @meteficha
• [x] pagerduty - Brendan Hay brendan.g.[email protected] @brendanhay
• [x] stack - Emanuel Borsboom [email protected] @borsboom

[brendanhay]

@bergmark: Where are you seeing these build failures? Are these via matrix.hacakge.* or via the stackage builder?

[phadej]

@brendanhay we build the whole stackage with new aeson already (--allow-newer kind of way)

[rubik]

@bergmark Hi, I'm the maintainer of argon. In my cabal file I have aeson >= 0.8. What should I do exactly?

[bergmark]

@rubik there's a compilation error you need to fix.

[phaazon]

smoothie-0.4.2.2 just added support for aeson-0.11.

[fosskers]

Upped microlens-aeson upper limit for aeson.

[tibbe]

Can you include instructions on how to build with the newer aeson on stack? stack build doesn't work with resolver: nightly-2016-02-10, it still picks aeson 0.9.0.1.

[snoyberg]

You can add an extra-dep to your stack.yaml file, e.g.:

extra-deps:

• aeson-0.11.0.0

On Wed, Feb 10, 2016 at 10:05 AM, Johan Tibell [email protected]
wrote:

Can you include instructions on how to build with the newer aeson on
stack? stack build doesn't work with resolver: nightly-2016-02-10, it
still picks aeson 0.9.0.1.

—
Reply to this email directly or view it on GitHub
https://github.com/fpco/stackage/issues/1211#issuecomment-182246744.

[tibbe]

ekg and ekg-json done.

[rubik]

argon done. New version (0.4.1.0) pushed to Hackage.

[agrafix]

elm-bridge is done

[asilvestre]

haskell-neo4j-client is done, new version 0.3.2.1 pushed to hackage

[freizl]

new version hoauth2-0.5.3 pushed to hackage.

[CristhianMotoche]

The package twitter-feed-0.2.0.5 just uploaded to Hackage.

[stepcut]

userid, happstack-authenticate, clckwrks, and clckwrks-plugin-page should all be updated and on hackage.

[juhp]

Thanks

[juhp]

A couple of new ones:

• [x] lambdacube-compiler-0.4.0.1 (>=0.9 && < 0.11). Csaba Hruska csaba.[email protected] @csabahruska. @lambdacube3d
• [x] lambdacube-ir-0.2.0.0 (>=0.9 && < 0.11). Csaba Hruska csaba.[email protected] @csabahruska.

[phadej]

Can the new fresh list be generated? There is a lot of noise, and new ping might be a good idea.

[csabahruska]

fixed:
http://hackage.haskell.org/package/lambdacube-compiler-0.5.0.1
http://hackage.haskell.org/package/lambdacube-ir-0.3.0.0

[dmjio]

fixed:
http://hackage.haskell.org/package/stripe-haskell-2.0.3
http://hackage.haskell.org/package/stripe-core-2.0.3
http://hackage.haskell.org/package/stripe-http-streams-2.0.3
in https://github.com/dmjio/stripe/pull/30

[k-bx]

riak is fixed http://hackage.haskell.org/package/riak-1.0.0.1

[bergmark]

There are now two packages that have been disabled because they need aeson 0.11; bloodhound and katip-elasticsearch

[juhp]

I see pandoc.git allows aeson-0.11 now. Pandoc looks like the biggest blocker currently in terms of revdeps.
Maybe @jgm can comment on plans for the next pandoc release?

Also servant-server and webdriver have some number of revdeps: and probably Michael's packages also I imagine but didn't check.

Probably good to run stackage-curator again to check for any new issues like:

• [x] ratel-0.1.0 (==0.9.*). Taylor Fausak [email protected] @tfausak. @tfausak

which first appeared in #1261.

[tfausak]

I released ratel-0.1.1 10 days ago with support for newer versions of Aeson.

[soenkehahn]

Just released servant-0.4.4.7 which allows aeson-0.11.*.

[DanBurton]

We're left with under a dozen packages on the naughty list. Please be advised that Stackage nightly builds will be switching over to aeson-0.11 soon, and any offending packages will be temporarily disabled from the build.

aeson-0.11.1.1 depended on by:

• datadog-0.1.0.1 (>=0.8 && < 0.10). Ian Duncan [email protected] @iand675. @iand675
• dixi-0.6.0.5 (>=0.8 && < 0.11). Liam O'Connor [email protected]. @liamoc
• flowdock-0.3.0.1 (>=0.8 && < 0.10). Ian Duncan [email protected] @iand675. @brewtown
• haxl-0.3.1.0 (>=0.6 && < 0.11). Oleg Grenrus oleg.[email protected] @phadej. @facebook
• hpc-coveralls-1.0.3 (>=0.7.1 && < 0.11). Michael Snoyman [email protected] @snoyberg. @guillaume-nargeot
• ihaskell-0.8.3.0 (>=0.7 && < 0.11). Andrew Gibiansky andrew.[email protected] @gibiansky. @gibiansky
• ipython-kernel-0.8.3.0 (>=0.6 && < 0.11). Andrew Gibiansky andrew.[email protected] @gibiansky. @gibiansky
• pandoc-1.16.0.2 (>=0.7.0.5 && < 0.11). John MacFarlane [email protected] @jgm. @jgm
• pandoc-citeproc-0.9 (>=0.7 && < 0.11). John MacFarlane [email protected] @jgm. @jgm
• servant-yaml-0.1.0.0 (>=0.8.0.2 && < 0.11). Oleg Grenrus oleg.[email protected] @phadej. @phadej
• yesod-auth-oauth2-0.1.7 (>=0.6 && < 0.11). Paul Harper [email protected]. @thoughtbot

[phadej]

Made revisions for haxl and servant-yaml

[juhp]

Thanks - down to 9 packages now. :)

[jgm]

I've just released pandoc 1.17, allowing aeson 0.11. Hope
this allows you to move forward.

+++ Jens Petersen [Mar 17 16 03:45 ]:

I see pandoc.git allows aeson-0.11 now. Pandoc looks like the biggest
blocker currently in terms of revdeps.
Maybe [1]@jgm can comment on plans for the next pandoc release?

[k-bx]

Just to not forget, latest pandoc-citeproc allows aeson 0.11 as well

[k-bx]

ihaskell and ipython-kernel should be fixed

[jferris]

I just merged and released version 0.1.8 yesod-auth-oauth2 allowing aeson 0.11. Thanks, @k-bx.

[liamoc]

Fixed dixi

[juhp]

Wow, thanks Guys! - this is really great.
We're down to just a few now. :-)

aeson-0.11.1.1 is out of bounds for:

• datadog-0.1.0.1 (>=0.8 && < 0.10). Ian Duncan [email protected] @iand675. @iand675
• flowdock-0.3.0.1 (>=0.8 && < 0.10). Ian Duncan [email protected] @iand675. @brewtown
• hpc-coveralls-1.0.3 (>=0.7.1 && < 0.11). Michael Snoyman [email protected] @snoyberg. @guillaume-nargeot

Additionally (#1296) pandoc-1.17 needs 3 other packages to be updated.

Also argon is also going to cause problems #1215, but we could disable it if needed.

datadog, flowdock, and hpc-coveralls also don't have any consumers in Stackage, so I think we could disable them if needed for moving to aeson-0.11.

[juhp]

Latest dixi requires servant-0.5 (#1290).

[juhp]

Current plan is to wait a little more for BlogLiterately-diagrams to support pandoc-1.17, and then move to aeson-0.11 and pandoc-1.17, and temporarily disable hpc-coveralls, dixi (sorry, because of needing servant-0.5), datadog, flowdock, and argon. Of course they can be re-enabled as soon as they support aeson-0.11. Hope this plan sounds okay.

[liamoc]

Why does servant-0.5 lead to dixi being disabled? Is it simply not being included in stackage yet?

[juhp]

@liamoc we currently have a constraint on servant see #1290 - so we would re-enable dixi as soon as servant-0.5 is ready for Stackage Nightly. (Edit: Alternative would be to disable some of the servant consumers that have not been updated yet to 0.5, which may still happen depending on how long they take...)

[liamoc]

OK, that's fine. It's not possible for dixi to work on both 0.4 and 0.5, so this solution seems best.

[juhp]

Okay thanks for understanding.

[juhp]

Leaving this open still since there could still be some build issues as Adam also mentioned earlier.

[brendanhay]

:relieved:

[juhp]

Thank you everyone for all the work on this!

Should be in 2016-03-24 Nightly, which is being pushed now.

[killy971]

https://github.com/guillaume-nargeot/hpc-coveralls is now fixed in version 1.0.4.
Sorry for the delay.