Many packages blocked on Stackage nightly for GHC 8.2.1

36 views
Skip to first unread message

Dan Burton

unread,
Jul 31, 2017, 5:15:05 PM7/31/17
to Stackage, haskell-cafe
Please be advised that many packages were dropped from the Stackage nightly build plan in order to arrive at a successful build with the new ghc. (Note that this does not affect the build plans for LTS 9.) This is to be expected whenever ghc gets a major version bump. For details, see: https://github.com/fpco/stackage/blob/master/MAINTAINERS.md

We have attempted to contact package authors whose packages were dropped. However, comprehensive notification is not fully automated, and there may be many who have not been directly contacted. You can check your section of build-constraints.yaml, as well as stackage.org/nightly, to see which of your packages are currently absent from the build plan.

You may restore your packages to the nightly build plan (once they are buildable with ghc 8.2.1) in the same way they were added: by opening a PR, uncommenting your packages in build-constraints.yaml.

Thank you for your efforts to keep the Haskell ecosystem up to date.

Dan Burton

unread,
Aug 4, 2017, 2:17:23 PM8/4/17
to David Turner, Stackage
It tends to be overkeen every time a new version of GHC comes around, as it is a significant amount of work to arrive at a working build plan. We've got to cut the build plan way down until we get to a snapshot that actually works. Once we get to a working state, we then start looking at adding things back in.

Compare:
https://www.stackage.org/nightly-2016-05-25 GHC 7.10, 1994 packages
https://www.stackage.org/nightly-2016-05-26 GHC 8.0, 1167 packages

https://www.stackage.org/nightly-2017-07-25 GHC 8.0, 2509 packages
https://www.stackage.org/nightly-2017-07-31 GHC 8.2, 1728 packages

I'm not sure how we pulled it off in one day last time, but the number of packages dropped is roughly 800 in both cases.

Although communications came out on 31 July, we'd been working on this for several days. Git blame shows that I wrote the commit that blocked your packages on 27 July, which explains why your updates on 28 July were not taken into account.

I hope that helps to give some insight into what's going on and why.

-- Dan Burton

On Thu, Aug 3, 2017 at 5:23 AM, David Turner <dave.c...@gmail.com> wrote:
Hi Dan,

I've just opened PR #2709 to reinstate the packages I maintain (https://github.com/fpco/stackage/pull/2709). As far as I could tell, I didn't have to do anything to them - I'd already pushed fixes to both to make them compile against base-4.10 on 28 July, a few days before your email came round. Not sure if this is what you expect, but it seems to me the process of dropping packages was a little over-keen this time round. No big deal, really, just thought I'd mention it.

Thanks to Dan and all for all the work put into maintaining Stackage.

Cheers,

David



_______________________________________________
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.


Reply all
Reply to author
Forward
0 new messages