Bug 1739975 - GHC 8.6 and Stackage LTS 13
Summary: GHC 8.6 and Stackage LTS 13
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-12 02:45 UTC by Ben Cotton
Modified: 2019-10-29 17:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-29 17:13:41 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ben Cotton 2019-08-12 02:45:28 UTC 
This is a tracking bug for Change: GHC 8.6 and Stackage LTS 13
For more details, see: https://fedoraproject.org/wiki/Changes/GHC_8.6

Update Haskell packages from GHC 8.4 to 8.6 and from Stackage LTS 12 to 13 package versions.
Comment 1 Jens Petersen 2019-08-13 10:05:38 UTC 
Building is largely complete in f31-ghc and the builds have been tagged in f31.
So this should be testable in the next Rawhide push and the F31 branch.
Comment 2 Ben Cotton 2019-08-13 16:48:42 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.
Comment 3 Jens Petersen 2019-08-21 12:14:23 UTC 
This has landed in Rawhide and branched to f31.
Comment 4 Ben Cotton 2019-08-27 17:17:56 UTC 
We have reached the '100% Code Complete' milestone in the Fedora 31 release cycle. If your Change is complete, please set the status to ON_QA. The Beta Freeze is underway. If you need a freeze exception, see https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

If this Change will not be ready for Fedora 31, please set the version to rawhide.
Comment 5 Ben Cotton 2019-08-29 18:44:24 UTC 
Moving to ON_QA based on comment 3
Comment 6 Ben Cotton 2019-10-29 17:13:41 UTC 
Closing Change tracking bugs for the Fedora 31 release.
Note You need to log in before you can comment on or make changes to this bug.