Bug 2080355 - Haskell GHC 9.2 & Stackage LTS 20
Summary: Haskell GHC 9.2 & Stackage LTS 20
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
Depends On: 2166028
Blocks: F38Changes
TreeView+ depends on / blocked
 
Reported: 2022-04-29 14:03 UTC by Ben Cotton
Modified: 2023-04-18 14:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-18 14:06:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-632 0 None None None 2022-10-17 13:59:50 UTC

Description Ben Cotton 2022-04-29 14:03:43 UTC
This is a tracking bug for Change: Haskell GHC 9.0 & Stackage LTS 19
For more details, see: https://fedoraproject.org/wiki/Changes/Haskell_GHC_9.0_%26_Stackage_19

The GHC Haskell compiler will be updated from major version 8.10 to 9.0,
and Haskell packages will be updated from Stackage LTS 18 to LTS 19 versions.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Jens Petersen 2022-07-13 14:25:34 UTC
A heads-up that I think I will have to defer this very major version change to after branching and hence Fedora 38.
I am currently still consumed with backporting the current Rawhide Haskell package set to EPEL 9.

However I am planning to submit the minor version updates already in Rawhide shortly as a separate Self-contained F37 Change.
So F37 users still have this smaller Haskell Change to look forward to.

Comment 2 Carlos O'Donell 2022-07-13 21:20:54 UTC
(In reply to Jens Petersen from comment #1)
> A heads-up that I think I will have to defer this very major version change
> to after branching and hence Fedora 38.
> I am currently still consumed with backporting the current Rawhide Haskell
> package set to EPEL 9.
> 
> However I am planning to submit the minor version updates already in Rawhide
> shortly as a separate Self-contained F37 Change.
> So F37 users still have this smaller Haskell Change to look forward to.

I'll be tracking this closely since the GHC 9 upgrade allows me to switch libffi to static trampolines to issues with ruby.

If you change in F38 then I'll update libffi at that time also. Thanks.

Comment 3 Jens Petersen 2022-07-14 06:10:12 UTC
(In reply to Carlos O'Donell from comment #2)
> I'll be tracking this closely since the GHC 9 upgrade allows me to switch
> libffi to static trampolines to issues with ruby.
> 
> If you change in F38 then I'll update libffi at that time also. Thanks.

Okay, thanks Carlos - that is good to know.

BTW we will still have the ghc8.10 package in Fedora for the foreseeable future.
Would that need special care or need a workaround to continue working?

Comment 4 Florian Weimer 2022-07-14 07:08:16 UTC
(In reply to Jens Petersen from comment #3)
> BTW we will still have the ghc8.10 package in Fedora for the foreseeable
> future.
> Would that need special care or need a workaround to continue working?

It's blocking the transition. As far as I understand it, the GHC developers have already declined fixing this issue in the 8.x series.

Comment 5 Carlos O'Donell 2022-07-14 17:00:35 UTC
(In reply to Florian Weimer from comment #4)
> (In reply to Jens Petersen from comment #3)
> > BTW we will still have the ghc8.10 package in Fedora for the foreseeable
> > future.
> > Would that need special care or need a workaround to continue working?
> 
> It's blocking the transition. As far as I understand it, the GHC developers
> have already declined fixing this issue in the 8.x series.

If we could compile GHC 8 with a bundled libffi it would unblock the system libffi transition to static trampolines?

Would we need a FesCo exception for bundling libffi for the duration of GHC 8's lifetime in Fedora?

Comment 6 Jens Petersen 2022-07-17 07:07:27 UTC
(In reply to Carlos O'Donell from comment #5)
> If we could compile GHC 8 with a bundled libffi it would unblock the system
> libffi transition to static trampolines?
> 
> Would we need a FesCo exception for bundling libffi for the duration of GHC
> 8's lifetime in Fedora?

Yes indeed, I think we can do that, yep (I just came back here to say the same thing:-)

Comment 7 Jens Petersen 2022-07-18 04:54:36 UTC
I have just changed the version field now to Fedora 38.

And created https://fedoraproject.org/wiki/Changes/Haskell_GHC_8.10.7 to replace it for F37.

Comment 8 Jens Petersen 2022-07-18 05:13:50 UTC
Ben, could you please change the status tag category of https://fedoraproject.org/wiki/Changes/Haskell_GHC_9.0_%26_Stackage_19 to be for F38?
(Currently still says ChangeAcceptedF37)  Or can I do it? :-)

Comment 9 Ben Cotton 2022-07-18 13:22:06 UTC
Wiki (and release notes issue) updated to reflect new version.

Comment 10 Jens Petersen 2023-01-10 16:01:49 UTC
A few things:

1. Currently this change is running slightly late - though I would still like to land it in F38.
   Looks like it will not happen in time for the mass-rebuild though. :-(

2. I have been struggling a bit with bundling libffi in ghc8.10...

3. I would like to skip ghc-9.0 and go straight to ghc-9.2 hopefully (to be confirmed).

Comment 11 Ben Cotton 2023-02-07 14:27:33 UTC
Today we reached the Code Complete (Testable) milestone on the F38 schedule: https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html

At this time, all F38 Changes should be complete enough to be testable. You can indicate this by setting this tracker to the MODIFIED status. If the Change is 100% code complete, you can set the tracker to ON_QA. If you need to defer this Change to F39, please NEEDINFO me.

Changes that have not reached at least the MODIFIED status will be given to FESCo for evaluation of contingency plans.

Comment 12 Jens Petersen 2023-02-16 07:55:57 UTC
I am still actively working on this in f38-build-side-62436
after overcoming various hurdles and still expect to finish it by next week.

Comment 13 Fedora Update System 2023-02-21 05:16:40 UTC
FEDORA-2023-7a3a4921e3 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7a3a4921e3

Comment 14 Fedora Update System 2023-02-21 08:07:41 UTC
FEDORA-2023-7a3a4921e3 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2023-02-21 08:10:34 UTC
FEDORA-2023-7a3a4921e3 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2023-02-21 08:13:24 UTC
FEDORA-2023-7a3a4921e3 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Jens Petersen 2023-03-28 07:41:35 UTC
As of the next f38 updating-testing push, upgrades from F37 to F38 should now also work well.
So I consider this done now.


Note You need to log in before you can comment on or make changes to this bug.