Handle shallow clone build failure with Github Workflow (ensure PEP 440) #5414
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.
bcc's GitHub workflow has been failing for a while when building from
a shallow clone (git clone --depth 1). In this case, git_describe()
from CMake returns an invalid version string (128-NOTFOUND-deadbeef).
Older setuptools versions used in Fedora 38 tolerated this format, but
newer setuptools in Ubuntu 24.04 enforces PEP 440 compliance and treats
it as an error, breaking the CI build.
This updates cmake/version.cmake to detect this case and fall back to a
compliant
0.0.0+<hash>version when tags are missing. The commit hash iskept for traceability, and behavior with full clones remains unchanged.