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

Image refresh for fedora-42 #7455

Merged
merged 1 commit into from
Feb 24, 2025
Merged

Conversation

cockpituous
Copy link
Contributor

@cockpituous cockpituous commented Feb 18, 2025

Image refresh for fedora-42

  • image-refresh fedora-42

@github-actions github-actions bot added the bot label Feb 18, 2025
@cockpituous cockpituous changed the title Image refresh for fedora-42 WIP: 782736396b7d: [no-test] Image refresh for fedora-42 Feb 18, 2025
@cockpituous
Copy link
Contributor

@cockpituous cockpituous force-pushed the image-refresh-fedora-42-20250218-225732 branch from 8934366 to 233c5fa Compare February 18, 2025 22:57
@cockpituous
Copy link
Contributor

@cockpituous cockpituous changed the title WIP: 782736396b7d: [no-test] Image refresh for fedora-42 Image refresh for fedora-42 Feb 18, 2025
@martinpitt
Copy link
Member

Some FIPS regression in F42? Plus some trouble with anaconda, but that could be a flake.

@mvollmer
Copy link
Member

FIPS is fixed in cockpit-project/cockpit#21636. I'll land these in lock-step. But anaconda needs checking...

@mvollmer
Copy link
Member

But anaconda needs checking...

It is under investigation already.

Copy link
Member

@mvollmer mvollmer left a comment

Choose a reason for hiding this comment

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

Thanks bots!

@mvollmer mvollmer merged commit cf0175b into main Feb 24, 2025
13 of 15 checks passed
@mvollmer mvollmer deleted the image-refresh-fedora-42-20250218-225732 branch February 24, 2025 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants