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

Install SDK with package manager on ubuntu #5940

Closed
ludovicalarcon opened this issue Dec 20, 2019 · 2 comments
Closed

Install SDK with package manager on ubuntu #5940

ludovicalarcon opened this issue Dec 20, 2019 · 2 comments

Comments

@ludovicalarcon
Copy link

Hello,

I followed the documentation to install dotnet core sdk on ubuntu 18.04 and I cannot got v2.2.207

I want install both v3.1.100 and v2.2.207 but I got the previous version instead (2.2.402).

sudo apt-get install dotnet-sdk-3.1
sudo apt-get install dotnet-sdk-2.2
dotnet --info

image

@dagood
Copy link
Member

dagood commented Dec 20, 2019

To work around the version ordering with apt, you can use = to specify the version you want:

sudo apt-get install dotnet-sdk-2.2=2.2.207-1

To see all available versions:

(as of 2019-12-20)
$ apt-cache madison dotnet-sdk-2.2
dotnet-sdk-2.2 |  2.2.402-1 | ...
dotnet-sdk-2.2 |  2.2.401-1 | ...
dotnet-sdk-2.2 |  2.2.301-1 | ...
dotnet-sdk-2.2 |  2.2.300-1 | ...
dotnet-sdk-2.2 |  2.2.207-1 | ...
...
dotnet-sdk-2.2 |  2.2.102-1 | ...
dotnet-sdk-2.2 |  2.2.101-1 | ...
dotnet-sdk-2.2 |  2.2.100-1 | ...

The one you get without specifying a version follows the version number order with no understanding of the SDK's 1xx/2xx/3xx... "product bands", so you end up with 2.2.402-1 by default.

This is a problem, but I don't know a great way to solve it. It also means apt upgrade isn't working for 2.2 builds.

Our RPM packages have the same issue. (The workaround there uses - instead of =.)

(There's more on why new SDKs weren't released for the higher product bands at dotnet/core#3848, but it sounds like you're already aware of that.)

@leecow @vivmishra @dleeapho Do we know what we're going to do with this problem for the Linux packages?

@ludovicalarcon
Copy link
Author

Thanks for the work around and all the explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants