Skip to content
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

amazonka and amazonka-* packages GHC 9.8.1 compilation failure #7261

Open
alexeyzab opened this issue Jan 1, 2024 · 2 comments
Open

amazonka and amazonka-* packages GHC 9.8.1 compilation failure #7261

alexeyzab opened this issue Jan 1, 2024 · 2 comments

Comments

@alexeyzab
Copy link
Contributor

I had to disable a lot of the amazonka packages when upgrading Nightly to GHC 9.8.1 because all of them had errors similar to this one:

      /home/curators/work/unpack-dir/unpacked/amazonka-devops-guru-2.0-9ed82fecbe49299e09b98b6af706ccbf342ca8ba08b152f5600b63a9f22e7a11/gen/Amazonka/DevOpsGuru/Types.hs:426:5: error: [GHC-97219]
           Duplicate record field 'endTime' in export list:
              'PredictionTimeRange(..)' exports the field 'endTime'
              belonging to the constructor 'PredictionTimeRange'’
                imported from 'Amazonka.DevOpsGuru.Types.PredictionTimeRange' at gen/Amazonka/DevOpsGuru/Types.hs:823:1-52
              'AnomalyTimeRange(..)' exports the field 'endTime'
              belonging to the constructor 'AnomalyTimeRange'’
                imported from 'Amazonka.DevOpsGuru.Types.AnomalyTimeRange' at gen/Amazonka/DevOpsGuru/Types.hs:764:1-49
           Suggested fix: Perhaps you intended to use DuplicateRecordFields
           |
       426 |     PredictionTimeRange (..),
           |     ^^^^^^^^^^^^^^^^^^^^^^^^

cc @brendanhay

@ysangkok
Copy link
Contributor

See also this comment from jackdk, who does most of the development:

It sounds like amazonka will not be in lts-23 because amazonka won't get ready in time.

@ysangkok
Copy link
Contributor

If only curator supported assigning a revision that isn't necessarily the 0th (which it doesn't), then we could just take the revision that allows GHC 9.8 and use no-revisions to ignore the revision banning 9.8 and then use configure-args to set DuplicateRecordFields. But because nightly has crypton-1.0, which wasn't allowed in revision 0, it wouldn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants