-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Updated apt packages cause Ubuntu instructions to fail #227
Comments
Attempted to work around this:
Oops. |
I have the same error message related to libhostfxr. In my case, after a fresh installation on Ubuntu 14.04.
|
I am also seeing the same issue... Got a brand new laptop running Mint 17.2, did an apt-get upgrade, and then install dot net, as well as Code. Getting the exact same message when I type "dotnet new". |
I'm experimenting the same issue on Ubuntu 16.04 64bits. |
+1 for the exact same error on Travis CI. |
I think that web page for Ubuntu / Linux Mint install is not up to date. 1 - Please remove any previous versions of .NET Core from your system (as told on web page...) 2 - Download and install latest version from repository (using browser) From URL: 3 -From jskeet comment:
After that, the following worked for me (with Linux Mint 18, using the Ubuntu 16.04 repository):
|
@juanram the link seems to be for ubuntu 16.04, I am on ubuntu 14.04 (Mint 17.3) so when I try to install it it says "Dependency is not satisfiable: libstdc++6..." so I went ahead with
and that fixed it.
Thanks all. |
@juanram: There's a broader point here though - even if preview3 is ready and available (which surprises me anyway), releasing a subset of packages which breaks anyone who has installed preview2 is a really bad idea. Ideally (IMO) anyone explicitly installing preview2 would keep preview2 anyway, but if that's not possible, the update shouldn't break them. I suspect the problem is that some packages have been released but others haven't... I don't know enough about apt to say for sure. I don't like the idea of Travis breaking with no warning every time there's a new build available. |
@jplebre It dit because it was the only package that was updated from the repo. I was using The version (i.e. 000583-00-1) has to be the same It seems to be a dependencies/packaging problem. |
Got the same problem on Ubuntu 16.04 and |
@jskeet: I agree with you. Ideally, if you do a .deb package correctly, it will satisfy all dependencies (or, at least, warn about any unresolved dependency) so I think something was not done right: maybe they missed something. @jfaquinojr: In any case, I think that the people from the 'dotnet core' project should take a look at this issue. |
So, @aleks-sidorenko solution worked for me, if you are stuck with travis install:
# Install .net using linux CLI commands
- sudo sh -c 'echo "deb [arch=amd64] https://apt-mo.trafficmanager.net/repos/dotnet/ trusty main" > /etc/apt/sources.list.d/dotnetdev.list'
- sudo apt-key adv --keyserver apt-mo.trafficmanager.net --recv-keys 417A0893
- sudo apt-get update
- sudo apt-get -qq install dotnet-dev-1.0.0-preview2-003121
- sudo apt-get install dotnet-hostfxr-1.0.2 |
Yeah, it seems that version 1.0.1 of: so I removed 'previous' version (dotnet-dev-1.0.0-preview3-003203) with the script, and then just to clean all, and then I reinstalled dot-net-dev-1.0.0-preview2-003121 as jplebre tells:
and it also worked for me. Please, note that this is a PREVIEW release. Please, remember that for Ubuntu 14.04 or Linux Mint 17 you should use before install:
And for Ubuntu 16.04 or Linux Mint 18 you should use instead:
|
Ongoing development activity pushed a package to that feed which was incompatible with released versions of dotnet. Sorry about this. In order to resolve this, we've created a new feed called "dotnet-release" that will contain only the stable bits. It is recommended that you start using this feed in your CI scripts or on your dev machines. The getting started instructions on https://dot.net/core for Ubuntu are also being updated to reflect this. If you are installing this on your dev machine, please make sure that you purge the previously installed package and then remove all of its dependencies using the following: sudo apt-get purge dotnet-host
sudo apt autoremove Here are the steps you need to do for Ubuntu 14.04: sudo sh -c 'echo "deb [arch=amd64] https://apt-mo.trafficmanager.net/repos/dotnet-release/ trusty main" > /etc/apt/sources.list.d/dotnetdev.list'
sudo apt-key adv --keyserver apt-mo.trafficmanager.net --recv-keys 417A0893
sudo apt-get update
sudo apt-get install dotnet-dev-1.0.0-preview2-003121 Here are the steps you need to do for Ubuntu 16.04: sudo sh -c 'echo "deb [arch=amd64] https://apt-mo.trafficmanager.net/repos/dotnet-release/ xenial main" > /etc/apt/sources.list.d/dotnetdev.list'
sudo apt-key adv --keyserver apt-mo.trafficmanager.net --recv-keys 417A0893
sudo apt-get update
sudo apt-get install dotnet-dev-1.0.0-preview2-003121
|
@blackdwarf: That's great, thanks very much. I can certainly confirm that's fixed the Noda Time build :) |
@jskeet the pleasure is all mine. :) |
See dotnet/core#227 for background.
@jskeet How to set up .net core in production env. I just searched and found how to set up .net core sdk on ubuntu. IMO, for production env, sdk is a little over weight. |
@yajiya: That's really a question unrelated to this issue, to be honest. |
as seen dotnet/core#227
@jskeet would it be OK if we closed this issue? Seems like the core underlying issue has been addressed. @yajiya if you are thinking about how to run apps in production, we have guidance on that: https://docs.microsoft.com/en-us/dotnet/articles/core/deploying/index. |
Yup, will close the issue now. |
I first noticed this on Travis, e.g.
https://travis-ci.org/nodatime/nodatime/builds/145115426
Now having run
sudo apt-get update
andsudo apt-get upgrade
on local Linux boxed (Ubuntu 14.04 and Ubuntu 16.04) I get the same problem.Running
dotnet restore
gives an error of:It looks like this happened between 2016-07-15T15:30:00Z (my last successful Noda Time build) and 2016-07-16T10:16:00Z.
My guess is that after the weekend, there will be a lot of people noticing this...
The text was updated successfully, but these errors were encountered: