[release/9.0-staging] Fix Tizen linux-armel build#110614
Merged
akoeplinger merged 2 commits intorelease/9.0-stagingfrom Dec 11, 2024
Merged
[release/9.0-staging] Fix Tizen linux-armel build#110614akoeplinger merged 2 commits intorelease/9.0-stagingfrom
akoeplinger merged 2 commits intorelease/9.0-stagingfrom
Conversation
Contributor
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
Member
|
Infrastructure-only change, tell mode. Marking as Servicing-approved. /cc @carlossanlop |
jkotas
approved these changes
Dec 11, 2024
Member
|
/backport to release/8.0-staging |
Contributor
Author
|
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/12379759394 |
Contributor
Author
|
@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! |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
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.