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

The 3.1.0 dotnet-runtime-3.1 Linux packages say "3.1.0 Preview 3" in their descriptions (Debian + RPM) #3975

Closed
dagood opened this issue Dec 8, 2019 · 3 comments

Comments

@dagood
Copy link
Member

@dagood dagood commented Dec 8, 2019

Note that like the other issues with 3.1.0 (#3950), the package's description says 3.1.0 Preview 3, but it actually installs a build that is essentially 3.1.0 stable, and it should work fine.

I saw this comment on the blog post calling out the problem: https://devblogs.microsoft.com/dotnet/announcing-net-core-3-1/#comment-4170.


I've tried installing 3.1.0 on Ubuntu 19.04 and CentOS 7, and "3.1.0" is installed on the machine:

$ dotnet --info
...
  Microsoft.NETCore.App 3.1.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

However the package description says "3.1.0 Preview 3"

$ yum info dotnet-runtime-3.1
...
Summary     : Microsoft .NET Core Runtime - 3.1.0 Preview 3 Microsoft.NETCore.App

This seems to be the same underlying problem that's caused the other 3.1.0 "Preview 3" issues. When I looked into it earlier, I found there weren't any differences that should matter to Linux users: dotnet/runtime#492 (comment).

This may not be worth fixing until 3.1.1, due to the risk and cost in replacing the bad packages with the correct ones without advancing the patch version.

@leecow

@leecow

This comment has been minimized.

Copy link
Member

@leecow leecow commented Dec 9, 2019

Thanks for the tracking issue. Since this has the same root cause as the comments in #3950 and #3962, closing as a duplicate.

@leecow leecow closed this Dec 9, 2019
@dagood

This comment has been minimized.

Copy link
Member Author

@dagood dagood commented Dec 9, 2019

@leecow to make sure the info's reachable, do we plan to fix the Linux packages for 3.1.0 or not?

@leecow

This comment has been minimized.

Copy link
Member

@leecow leecow commented Dec 9, 2019

This will be fixed for all packages and installers exhibiting the behavior in 3.1.1 in January.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.