-
Notifications
You must be signed in to change notification settings - Fork 696
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
Fix #8377: allow text-2.0 and time-1.12 in cabal-install #8398
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
I think it looks fine, but need base bumps for haskellari/lukko#30 and phadej/singleton-bool#20, which I opened now :) (For anyone wondering it is possible to build cabal-install with ghc-9.4.1 using |
e2b7561
to
b17f24d
Compare
Also allow latest aeson, network-wait, optparse-applicative in cabal-testsuite.
Can a revision be done on Hackage now? |
The only code change in this PR is addressing a |
Yes, we'd need a manual (or in a special PR) test run with a constraint that forces these bounds. But that's on 3.8 branch, so only after this is backported. Let me backport... |
@mergify backport 3.8 |
✅ Backports have been created
|
Oh, actually the dev (default) version of cabal.project forces that, so it's enough to build and test with that one. |
Yeah, I couldn't get cabal to pick up the latest versions otherwise, so I forced it. |
The version obtained with
The testsuites do not build:
The dependency Are the testsuites of the released versions supposed to build? (If not we could delete them from the .cabal file before releasing.) |
That's a bummer. If they are in the .cabal file, they should build. Agreed we should either remove them or publish enough little packages for them to build. I suppose the former is easier and we have more urgent issues. Edit: ideally we'd remove them to yet another package so that they can stay there unmolested whenever we release cabal proper. |
Ok, pushed the revision: https://hackage.haskell.org/package/cabal-install-3.8.1.0/revisions/
|
@Mikolaj: Indeed, cabal-install-3.6.2.0 was released without any test suites. |
Oh, wouldn't it be better to test first? Not sure if the tests in the backport use the cabal.project or ignore it, but at least somebody could checkout 3.8 and test manually.
Let me open a ticket in that case. |
Indeed, this would be safer. Branch Unfortunately, the CI for the backport does not show whether |
I've rummaged in the logs and it seems it did not build text 2 even the first time it started on GHC 9.2, so it probably ignores cabal.project. Too bad, otherwise we'd have a test for free. Anyway, it should get merged soon, so if a volunteer would like to test, that's a good moment. Otherwise, we will depend on our luck. :) |
The backport is merged. |
Fix #8377: allow text-2.0 and time-1.12 in cabal-install.
Also allow latest aeson, network-wait, optparse-applicative in cabal-testsuite.