Skip to content

try Ubuntu 24.04 again #11068

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

geekosaur
Copy link
Collaborator

We had problems with their image last time. Let's see if they're fixed now.


Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

Copy link
Collaborator

@ulysses4ever ulysses4ever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sweet!

@geekosaur
Copy link
Collaborator Author

geekosaur commented Jul 12, 2025

I forget, did we decide to use ubuntu-latest so we catch this kind of breakage earlier or ubuntu-VERSION to avoid breakage?

We had problems with their image last time. Let's see if they're
fixed now.
@geekosaur
Copy link
Collaborator Author

geekosaur commented Jul 12, 2025

Whoops: old-ghcs still needs to be on 22.04 or earlier because 24.04 doesn't have the ancient ncurses and terminfo packages that ancient ghcs require. This might explode because a cabal built on 24.04 won't run, which would leave us on 22.04 until those old ghcs roll off support completely. (Or require validate-old-ghcs to rebuild everything first.)

@geekosaur geekosaur marked this pull request as ready for review July 12, 2025 02:32
@geekosaur
Copy link
Collaborator Author

Okay, apparently just running validate-old-ghcs in 22.04 is good enough. Seems to be ready to go, then.

Copy link
Member

@Mikolaj Mikolaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great news!

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

Successfully merging this pull request may close these issues.

3 participants