-
Notifications
You must be signed in to change notification settings - Fork 66
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ci: githubactions update to ubuntu 23.10
- Loading branch information
Showing
1 changed file
with
6 additions
and
6 deletions.
There are no files selected for viewing
This file contains 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
15d8224
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.
The Ubuntu version is intended to use 20.04
Or you might fail the line
auditwheel repair --plat manylinux_2_31_x86_64 dist/*.whl
We have targeted 20.04 so end-developers can use the library with an older version of glibc (2.31). Not everyone is running on Ubuntu 23.10.
15d8224
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 for notifying, I reverted this commit. Do you know some way how we can automatically build for several latest versions of glibc and python?
It would be best if we do not have to always update version lists.
15d8224
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.
In general, we won't update the "dependencies", which means the library we depend on, automatically.
Think of the case: we are designing a system that will automatically update a fundamental library.
The update on the fundamental library may introduce breaking changes, which means the latest version is not compatible with previous versions.
End-users of our system will need to update the fundamental library every time we change the version, automatically.
i.e. User needs to update their Linux version whenever we change the Linux version, automatically.
And that's the reason I mentioned "Not everyone is running on Ubuntu 23.10."
In practice, we will pin some fundamental library to a certain version, unless they have a critical bug / we can't solve our problem without upgrading it.
In this particular case, I pinned that to glibc 2.31, which means the Linux version around Ubuntu 20.04 is good. (which was released on 2020, 5 years of coverage)
When to move to a higher version of dependency is always an engineering decision, with trade-offs.
IMO, it is better to do it manually in this case. Especially we are distributing Pre-Compiled Library.
15d8224
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.
@khwong-c , you I right in all points.
I was thinking that we can do something like "for all versions newer than X" and keep releasing manually only on tag.
Do you know about any tool which we can use to query python and and glibc versions so we at least know that we are missing some versions?
I would like to get the list from this table https://www.python.org/downloads/ and then somehow compare it with the matrix definition in CI config. CI config is yaml so it is easy.
For mentioned link there has to be also some restapi to get it but I can not find it.
For glibc i did not find anything as well.