-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Aspnetcore doesn't look for linux-musl nupkgs when building on linux-musl platform #39822
Comments
Could/should we push this logic/fix into aspnetcore itself? I identified several other cases that would break in the ASP.NET Core builds a few months ago, including |
[Source-build triage] We agree with @omajid's suggestion that the preferred place to fix this is within aspnetcore itself. If guidance is needed, reach out to @dotnet/source-build-internal. |
Thanks @MichaelSimons. Do you think this is something we must fix? I'm trying to gauge the urgency and importance of this. |
@mkArtakMSFT - Must is a little strong. I would classify this as something we should fix/accept. This makes is easier for distro maintainers to build .NET from source. With the unified build investments being made in .NET 8 we want to support a true open source upstream vs what we have today where upstream is mostly Microsoft's variant. |
Considering the move to portable RIDs as default for source-build starting with .NET8, this should be worked on. Right now, I'm unable to build dotnet8 when |
A related issue is #37400, failing the build on non-x64 platform. A workaround is setting |
Aspnetcore looks for linux-x64 version of nupkgs that, under Alpine, should be linux-musl-x64.
Provisional patch follows:
Better implementation would involve, either Aspnetcore automatically setting os-name to linux-musl when building, or repos/aspnetcore.proj automaticallty adds the above BuildCommandArg. Ditto on repos/installer.proj for setting AspNetCoreSharedFxInstallerRid,
Made as part of Alpine Linux dotnet6 packaging project, see dotnet/source-build#2782
The text was updated successfully, but these errors were encountered: