I was following the procedure but ran into an error...
sudo apt-get install aspnetcore-runtime-2.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
aspnetcore-runtime-2.2 : Depends: dotnet-runtime-2.2 (>= 2.2.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Which distro did you try?
Does it happen on clean VM as well?
@dagood can you please help here?
@irreverencieux - could you run sudo apt-get install dotnet-runtime-deps-2.2? This should tell us exactly which system dependency is unable to be installed.
I had that same issue: https://github.com/dotnet/core/issues/2381
sudo apt-get update && sudo apt-get upgrade the re-run, that did the trick. From https://askubuntu.com/questions/1065231/dpkg-deb-error-archive-has-premature-member-control-tar-xz-before-contr/1065237#1065237
Possibly its the libicu57 package that won't install. Thats what happens to me. I have the same error on this thread.
Package libicu57 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
You could try using snap to install the beta.
@irreverencieux - could you run
sudo apt-get install dotnet-runtime-deps-2.2? This should tell us exactly which system dependency is unable to be installed.
It's libicu57 that won't install.
What's the next step here?
cc @tarekgh @janvorli
CC @rakeshsinghranchi
cc @dagood instead of @rakeshsinghranchi
Original poster's issue didn't have enough info to follow up on--closing as stale.
Thanks all for the input! To sum up:
sudo apt-get update && sudo apt-get upgrade (https://github.com/dotnet/core/issues/2381) may have fixed it, but we don't know. I've asked Lee in that thread if we can add something to the install page to inform people about this issue.