Aeson 1.2 state?

[qrilka]

#2449 was locked already more than a month ago, it was said that stackage curators will check it periodically so my question is - how large is that period? :)
I'm asking because aeson is 1 of obstacles for GHCJS support in lts-8 (see tolysz/ghcjs-stack#8 ) and with a locked issue it's not clear how to help pushing aeson-1.2 into LTS

[mihaimaruseac]

I checked now, there are still a few blockers:

aeson-1.2.0.0 (Adam Bergmark [email protected] @bergmark) is out of bounds for:

• clash-lib-0.7.1 (>=0.6.2.0 && < 1.2). Christiaan Baaij [email protected] @christiaanb. @clash-lang. Used by: library
• discord-hs-0.2.2 (>=1.0 && < 1.2). Joshua Koike [email protected] @Jano017. @Jano017. Used by: library
• haxl-0.5.0.0 (>=0.6 && < 1.2). Oleg Grenrus [email protected] @phadej. @facebook. Used by: library, test-suite
• idris-1.0 (>=0.6 && < 1.2). Jens Petersen [email protected] @juhp. @idris-lang. Used by: library
• katip-0.3.1.4 (>=0.6 && < 1.2). Ozgun Ataman [email protected] @ozataman. @Soostone. Used by: library, test-suite
• persistent-template-2.5.2 (>=0.7 && < 1.2). Michael Snoyman [email protected] @snoyberg. @snoyberg. Used by: library, test-suite
• profiteur-0.4.2.2 (>=0.6 && < 1.2). Jasper Van der Jeugt @jaspervdj. @jaspervdj. Used by: executable
• rest-types-1.14.1.1 (>=0.7 && < 1.2). Silk [email protected]. @bergmark @hesselink. Used by: library
• servant-swagger-1.1.2.1 (>=0.11.2.0 && < 1.2). Nickolay Kudasov [email protected] @fizruk. @soenkehahn @jkarni @phadej. Used by: library, test-suite
• servant-swagger-ui-0.2.2.2.2.8 (>=0.8.0.2 && < 1.2). Oleg Grenrus [email protected] @phadej. @phadej. Used by: test-suite
• servant-yaml-0.1.0.0 (>=0.8.0.2 && < 1.2). Oleg Grenrus [email protected] @phadej. @phadej. Used by: test-suite
• streaming-utils-0.1.4.7 (>0.8 && < 1.2). Michael Thompson [email protected] @michaelt. @michaelt. Used by: library
• ua-parser-0.7.3 (>=0.7 && < 1.2). Ozgun Ataman [email protected] @ozataman. @ua-parser. Used by: library, test-suite
• uri-bytestring-aeson-0.1.0.0 (>=0.11 && < 1.2). Simon Hafner [email protected] @reactormonk. @reactormonk. Used by: library

[reactormonk]

There is now uri-bytestring-aeson-0.1.0.1 with the correct bounds. For future reference, do I need to mention that here specifically, or does it get picked up automatically?

[phadej]

servant- packages are going to updated any moment now (verifying last one).

Stackage maintainers are free to drop haxl if Facebook folks don't release the compatible version in time (the PR have been merged for some time already, and seems there are preparations for GHC-8.2 happening in the repository)

[bergmark]

@qrilka we don't do major version upgrades in an LTS series so aeson-1.2.0.0 won't be included until
LTS 9 ships, at the earliest. (e haven't scheduled LTS 9 but it's about time for it).

[mihaimaruseac]

@reactormonk it gets picked up

[mihaimaruseac]

This is now also blocked by #2537

[qrilka]

@bergmark will there be some ticket in this tracker about lts-9 preparation here or on #2537 ? Probably this lts preparation process is documented somewhere?

[bergmark]

Sorry, I misspoke. What we usually do is take the current nightly and turn that into the next LTS since otherwise the LTS would contain packages that may not have been tested sufficiently. That means aeson-1.1.* would be in LTS 9 which should be fine for ghcjs as it has the flag for toggling FFI code.

That's really all there is to that process.

[christiaanb]

I've updated the .cabal file for clash-lib-0.7.1 on hackage with the correct bounds

[bergmark]

No need to keep this open as we have #2449, i may make a new issue out of it as only a few packages remain.