Repository navigation
[release/9.0-staging] Fix Tizen linux-armel build - #110614
akoeplinger merged 2 commits into
Conversation
Sorry, something went wrong.
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
Sorry, something went wrong.
|
Infrastructure-only change, tell mode. Marking as Servicing-approved. /cc @carlossanlop |
Sorry, something went wrong.
|
/backport to release/8.0-staging |
Sorry, something went wrong.
|
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/12379759394 |
Sorry, something went wrong.
|
@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 128Please backport manually! |
Sorry, something went wrong.
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:
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.