ci: Fix the FreeBSD CI run #8239
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cdecker
force-pushed
the
202504-fix-freebsd
branch
3 times, most recently
from
d7441a3 to
27fe6f8
Compare
We were overly specific in selecting `python38`. As that has now reached its EOL, the package to install would be `python39`, however there is a meta-pacakge `python3` that I think we can keep using without having to bump the package name on the next EOL event. Changelog-None
cdecker
force-pushed
the
202504-fix-freebsd
branch
from
27fe6f8 to
9f1c57b
Compare
cdecker
force-pushed
the
202504-fix-freebsd
branch
from
94055d1 to
6b35c57
Compare
Collaborator
|
Duplicate to #8229? |
Member
Author
|
Sure |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We were overly specific in selecting
python38. As that has nowreached its EOL, the package to install would be
python39, howeverthere is a meta-pacakge
python3that I think we can keep usingwithout having to bump the package name on the next EOL event.