-
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
.NET Core 2.1 #1614
Comments
Link to "Known Issues" from here is also returning 404. |
@uffebjorklund and @winzig - both should be up now. |
@jnm2 - fixed! |
The ubuntu packages for bionic seem to be missing "dotnet-sdk-2.1.300" and reverts to installing the preview. It looks like the package "dotnet-sdk-2.1" is pointing to the correct deb file though. |
@annymsMthd - We need to make an update to the install instructions so to refer to cc @rowanmiller |
I have a weird issue with the trusty repo (perhaps other ubuntu repos are also affected).. I'm using a mirroring too to mirror the entire repo for installation inside a segragated network consisting of hundreds of machines. Unfortunately, one of packages in the repo seems to have a bad hash value in the Packages file... While the package itself (addlogin) is not a dependency of dotnet-sdk-2.1.300 in itself, the mirroring tool has no way of knowing this, and fails on the hash mismatch regardless... Here's is the information: The 2.1.200 SDK depends on "aadlogin-selinux_1.0.004870001_amd64.deb" but the hash mismatches GeneralWhen I do:
If you download the package release file:
The package is signed with the following hashes:
I'm guessing something got messed up? |
@damageboy - I'll check with the product repo owners with respect to the hash. Where are you seeing that the SDK has a dependency on aadlogin? The only defined dependencies are on aspnetcore-runtime and dotnet-runtime and it's not a dependency through any of the other packages. Also, do you mind if I pull your comment up into an issue by itself? |
While installing .NET Core 2.1 in Fedora 27, I can see some dependent packages are RC version. Is it expected?
|
dotnet-sdk 2.1.300 still show an outdated message when first init. Maybe it's no longer needed as I can found it in Updated: I see the message was removed in dotnet/cli#8957, but the translations are never updated, so the message still left for all other languages. |
Can we install it to Win7 without sp1? |
The Known Issues page does not list a known issue we hit (and a pretty big one). The Alpine .NET Core images will segfault on a host running with SELinux on. dotnet/dotnet-docker#561 |
@leecow That is why even if there is NO dependency on addlogin through, for example, installing dotnet-sdk-2.1.300... The mirroring tool doesn't care or know about that. As far as a mirroring tool would be concerned it's all or nothing. And the moment it sees an hash mismatch on the Package release files, it's game over. Again... Stressing that this is a less than standard situation, since what is failing is the apt repo MIRRORING rather than the installation. I've previously opened an issue about this before, during the RC1 phase... |
@tanaka-takayoshi - we're aware of the issue and tracking in #1620 |
@damageboy - contacting the repo admins to see if they can resolve. |
Looks like .NET Core 2.1 is broken on Arch Linux. I'm having the same issues as this person here: https://stackoverflow.com/questions/50689340/asp-net-core-2-1-on-arch-linux-does-not-run I'm trying to run this project (simple project to just play with signalr 2.1 and such). https://github.com/JesseObrien/signalr-jwt Error:
Same package installed, same
|
You likely need to copy aspnet into the right location. Should work if you do that an console apps run fine. |
This page doesn't have instructions or package links for .NET Core 2.1 in the "Install .NET Core for supported Red Hat Enterprise Linux (RHEL) versions" section: Are the RHEL packages still being finalized for .NET Core 2.1? |
It looks like the release candidate files were removed and replaced by the official release files. The yum package for dotnet-sdk-2.1.0 should be updated to download the new files.
|
@mrichards3 rpms for RHEL should be available this week. We'll update those instructions once they are available. |
To add to what @KevinKibler said, it looks like the dependency tree still refers to some of the rc files that were deleted. You can reproduce this easily with docker:
Here is the relevant bit of output:
|
I'm getting the same error downloading a previous release using Can someone fix this please? and maybe a test should be written for this... |
I am getting the same issue as well, with any flavor of 2.1.x thanks |
Also having the same issue with missing You can work around it by explicitly installing version Probably related to work being done in #1620 :
|
@mrichards3 - yes, the RHEL release is still being finalized. Talked with the Red Hat folks yesterday and they're on track to release next week. |
The RHEL rpms are available, you can install and use .NET Core 2.1 as follows:
RHEL container images (and documentation) are expected in 1 to 2 weeks. |
Closing this issue now that 2.1.1 is released. |
.NET Core 2.1.0
Blog post
Release Notes
Please report any issues you find with 2.1, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:
The text was updated successfully, but these errors were encountered: