-
Notifications
You must be signed in to change notification settings - Fork 676
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
Build failure with GHC-8.2 #9952
Comments
The bad commit is 54183f2, old GHC support breakage seems unintentional. |
It passed old GHCs |
But the problem is when building with GHC-8.2? It's out of the support window. Oldest tested for compilation is GHC 8.6.5. I don't think we announce when GHCs drop out of our support window. Should we? It happens without any action. We could announce when we spot it and adjust CI. If so, that should be added to the criteria stating when a changelog is necessary. |
That is a problem, though. Whenever we drop a GHC from CI we should bump the bounds and I think usually we do, so it's not unclear, I think. |
First, please make a Hackage revision so the builds are not failing and then we can discuss further. This is criticial issue, you should act ASAP. |
Which revision would fix this? |
I think Cabal-syntax bound on |
Here's a list of which |
@ffaf1: you have full authority to do just that revision, if you'd like to. I'd announce it on the channel, though, for transparency and in case we missed something. |
I am going to download GHC 8.4.2 locally, make sure it compiles, make an announcemente on Matrix and then do a revision setting edit: with GHC 8.4.2 I got this error
*8.4.4. works fine so it will still be |
Revision has been published. |
@ffaf1 Thanks
You definitely should. Dropping support for old GHCs, Virtually all maintainers do so, e.g. https://hackage.haskell.org/package/containers-0.6.6/changelog; it's the first line in the changelog. Also previously such changes were announced in Cabal's changelog, though not very prominently cabal/release-notes/Cabal-3.10.1.0.md Line 131 in c80ee75
EDIT: FWIW, there's also some cleanup you could do, a simple
There's also |
I forgot to mention an important point: having metadata updated and changelog entry means that there is a record in VCS when the change happened, leaving some trace. If the change is only in some CI configuration, it may looks like an accident. And so far it looks so to me. I don't know whether to expect |
Release notes are being updated in #9953. |
I think the only major remaining task in this issue is a PR that fixes the base bound on master and a backport to 3.12. Am I right? Volunteers? |
It's been merged and backported. Is there anything else we could do? If not, shall we close this ticket? |
Failed to build Cabal-syntax-3.12.0.0.
Have someone forgot adjusting lowerbounds? Has Cabal-syntax dropped support for GHC-8.0 and GHC-8.2 (I dont' see a mention in the changelog).
The text was updated successfully, but these errors were encountered: