ci: Fix LKM version number anomaly and Git ownership issues#2832
Merged
Ylarod merged 1 commit intotiann:mainfrom Oct 28, 2025
Prslc:main
Merged
ci: Fix LKM version number anomaly and Git ownership issues#2832Ylarod merged 1 commit intotiann:mainfrom Prslc:main
Ylarod merged 1 commit intotiann:mainfrom
Prslc:main
Conversation
Signed-off-by: Prslc <[email protected]>
Ylarod
approved these changes
Oct 28, 2025
u9521
pushed a commit
to u9521/KernelSU
that referenced
this pull request
Dec 31, 2025
**Fix LKM version number anomaly and Git ownership issues** The issue, introduced in commit cf361a7, was caused by a user permission mismatch between the Docker container and the host, which made Git detect "suspicious ownership" and blocked proper version retrieval during the build. Added `git config --global --add safe.directory` to bypass Git's ownership check, allowing the KernelSU module to build correctly in CI pipelines and retrieve the correct version number. Signed-off-by: Prslc <[email protected]>
u9521
pushed a commit
to u9521/KernelSU
that referenced
this pull request
Jan 3, 2026
**Fix LKM version number anomaly and Git ownership issues** The issue, introduced in commit cf361a7, was caused by a user permission mismatch between the Docker container and the host, which made Git detect "suspicious ownership" and blocked proper version retrieval during the build. Added `git config --global --add safe.directory` to bypass Git's ownership check, allowing the KernelSU module to build correctly in CI pipelines and retrieve the correct version number. Signed-off-by: Prslc <[email protected]>
u9521
pushed a commit
to u9521/KernelSU
that referenced
this pull request
Jan 5, 2026
**Fix LKM version number anomaly and Git ownership issues** The issue, introduced in commit cf361a7, was caused by a user permission mismatch between the Docker container and the host, which made Git detect "suspicious ownership" and blocked proper version retrieval during the build. Added `git config --global --add safe.directory` to bypass Git's ownership check, allowing the KernelSU module to build correctly in CI pipelines and retrieve the correct version number. Signed-off-by: Prslc <[email protected]>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix LKM version number anomaly and Git ownership issues
The issue, introduced in commit cf361a7, was caused by a user permission mismatch between the Docker container and the host, which made Git detect "suspicious ownership" and blocked proper version retrieval during the build.
Added
git config --global --add safe.directoryto bypass Git's ownership check, allowing the KernelSU module to build correctly in CI pipelines and retrieve the correct version number.