You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This results in failed builds if Ubuntu 22.10 is targeted.
Reproduction Steps
mkdir HelloWorld && cd HelloWorld
dotnet new console
dotnet build -r ubuntu.22.10-x64 --self-contained -c Release
Expected behavior
should build successful
Actual behavior
/usr/lib/dotnet/sdk/X.0.1XX/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(90,5): error NETSDK1083: The specified RuntimeIdentifier 'ubuntu.22.10-x64' is not recognized. [/home/USER/HelloWorld/HelloWorld.csproj]
Build FAILED.
Regression?
No.
Known Workarounds
Canonical already has a patch for this problem and I prepared a fork to open Pull Requests for main, release/6.0, release/7.0. Before opening the PRs I want to ask if there are any reasons against applying this patch, as the original patch is more than a year old (4. March 2022 by wfurt tweinfurt@yahoo.com).
Configuration
dotnet6, dotnet7, dotnet8
Other information
Ubuntu 22.10 kinetic kudu is a non-LTS release and reaches its end of life in July 2023. Nonetheless other ubuntu non-LTS RIDs are also present in the configuration files. Additionally dotnet6 and dotnet7 are currently packaged by Canonical for Ubuntu 22.10 kinetic kudu.
Description
The Ubuntu 22.10 kinetic kudu runtime identifiers are currently missing in the following files:
src/libraries/Microsoft.NETCore.Platforms/src/runtime.jsonsrc/libraries/Microsoft.NETCore.Platforms/src/runtime.compatibility.jsonsrc/libraries/Microsoft.NETCore.Platforms/src/runtimeGroups.propsThis results in failed builds if Ubuntu 22.10 is targeted.
Reproduction Steps
Expected behavior
should build successful
Actual behavior
Regression?
No.
Known Workarounds
Canonical already has a patch for this problem and I prepared a fork to open Pull Requests for
main,release/6.0,release/7.0. Before opening the PRs I want to ask if there are any reasons against applying this patch, as the original patch is more than a year old (4. March 2022 by wfurt tweinfurt@yahoo.com).Configuration
dotnet6, dotnet7, dotnet8
Other information