Skip to content
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

After updating to 5.0.200-1 using package manager, it appears that no sdks are installed. #49375

Closed
ac10n opened this issue Mar 3, 2021 · 8 comments
Assignees
Milestone

Comments

@ac10n
Copy link

ac10n commented Mar 3, 2021

OS: Fedora 33.

Last night I dnf distro-syncd my system as usual, and there was this .net sdk update to 5.0.200-1.

After that, dotnet --list-sdks shows no results and my .net programs fail to compile.

More info: I've been using .net on this system before .net 5 and have installed all updates to .net without any similar problems.

Also, doing sudo dnf install dotnet-sdk-5.0 does nothing, complaining: Package dotnet-sdk-5.0-5.0.200-1.x86_64 is already installed.

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@marcpopMSFT marcpopMSFT self-assigned this Mar 4, 2021
@marcpopMSFT
Copy link
Member

@dleeapho who usually investigates package manager issues?

@ac10n
Copy link
Author

ac10n commented Mar 4, 2021

Temporary Workaround:

Doing sudo dnf install dotnet-sdk-5.0-5.0.103-1.fc33.x86_64 Fixed this temporarily for me, as my package manager insists that it has updates, and on next update it'll nuke the sdk again.

This allowed me to do my work, while we wait for a more serious solution. Meanwhile, I need to prevent this package from being updated: sudo dnf upgrade --exclude=dotnet-sdk-5.0.x86_64

@ghost
Copy link

ghost commented Mar 5, 2021

I've run into the same issue. Fedora 33, installing dotnet-sdk-5.0-5.0.200 results in no SDK content under /usr/lib64/dotnet/sdk/ (as was the case for dotnet-sdk-5.0-5.0.103).

5.0.200 SDK content (as installed by dotnet-sdk-5.0-5.0.200) seems to have been moved to /usr/share/dotnet/sdk/5.0.200 , but dotnet host tools doesn't pick that up?

No errors in /var/log/dnf.log.

@dotnet-issue-labeler dotnet-issue-labeler bot added area-Setup untriaged New issue has not been triaged by the area owner labels Mar 9, 2021
@dleeapho dleeapho transferred this issue from dotnet/sdk Mar 9, 2021
@dleeapho
Copy link

dleeapho commented Mar 9, 2021

Moved to dotnet/runtime to investigate package issue.

@ac10n
Copy link
Author

ac10n commented Mar 10, 2021

@dleeapho Please note that this update does not remove the runtime (I think I've checked this). It removes the sdk.

@ac10n
Copy link
Author

ac10n commented Mar 10, 2021

Today I got new updates: 5.0.201 and with installing them, my problem is solved.

@NikolaMilosavljevic
Copy link
Member

Main issue tracked in #47500

@NikolaMilosavljevic NikolaMilosavljevic removed the untriaged New issue has not been triaged by the area owner label Mar 10, 2021
@NikolaMilosavljevic NikolaMilosavljevic self-assigned this Aug 6, 2021
@NikolaMilosavljevic NikolaMilosavljevic added this to the 6.0.0 milestone Aug 6, 2021
@jeffhandley jeffhandley modified the milestones: 6.0.0, 6.0.x Nov 22, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Oct 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants