-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
openSUSE - upgrade using 'zypper up' command upgrades 3.1 host to 6.0 and removes 'dotnet' command #61849
Comments
I've confirmed this issue on openSUSE and other RPM-based distros (i.e. CentOS). It is a regression. In .NET 3.1 and 5.0 we were creating a
In 6.0 after infra refactoring we had a bug where we weren't setting any symlinks. Later we fixed it to create symlink in an
However, new symlink is created in It's unclear why we ended up with |
The workaround is to create a symlink using the following command:
|
The installer can cleanup the existing symlinks in both known locations and create the new one. |
Why is that the case? From an outsider's PoV it doesn't make a lot of sense to have everything versioned except for the main package which will just freely upgrade to the latest .Net version. |
The original issue was fixed in January. |
Dotnet-host package is built with version-agnostic package name, which causes an issue when upgrading, for instance 3.1 host to latest. 6.0 host will be installed and 'dotnet' command will be missing.
Dotnet-host package is intentionally built as version-agnostic, see relevant infra:
runtime/src/installer/pkg/sfx/installers/dotnet-host.proj
Line 15 in 4e2d3a6
https://github.com/dotnet/arcade/blob/97463777ee9a8445d4a4c5911ede0f0cd71fa8aa/src/Microsoft.DotNet.Build.Tasks.Installers/build/installer.singlerid.targets#L99
Upgrading to latest host version should not remove 'dotnet' command.
The text was updated successfully, but these errors were encountered: