-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[release/9.0-staging] Fix Tizen linux-armel build #110614
[release/9.0-staging] Fix Tizen linux-armel build #110614
Conversation
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
Infrastructure-only change, tell mode. Marking as Servicing-approved. /cc @carlossanlop |
/backport to release/8.0-staging |
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/12379759394 |
@akoeplinger backporting to release/8.0-staging failed, the patch most likely resulted in conflicts: $ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch
Applying: Fix linux-armel build
Applying: Try the dynamic approach
error: sha1 information is lacking or useless (eng/common/cross/toolchain.cmake).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 Try the dynamic approach
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
Backport of #110514 to release/9.0-staging
/cc @akoeplinger @am11
Customer Impact
The linux-armel checked CoreCLR_NonPortable build is broken without this. It is an infrastructure-only change and only impacts testing CI jobs for Tizen.
Regression
Testing
CI Testing.
Risk
Low. Only affects CI testing jobs for Tizen.
IMPORTANT: If this backport is for a servicing release, please verify that:
release/X.0-staging
, notrelease/X.0
.Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.