I am getting error saying package not available #3870

dpanchal-visuallease · 2019-11-20T19:11:07Z

Problem encountered on https://dotnet.microsoft.com/download/linux-package-manager/sdk-3.0.101
Operating System:

Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

dagood · 2019-11-20T19:22:59Z

A few questions:

Which distro did you select in the dropdown?
What linux distro are you running?
What type of device are you using? (Raspberry Pi, for example, or ordinary desktop computer?)

Please also paste the commands you ran and their output here.

dpanchal-visuallease · 2019-11-20T19:46:26Z

Following commands were working fine via packer (since today morning), and it suddenly started failing. { "execute_command": "echo 'ec2-user' | {{.Vars}} sudo -S -E bash '{{.Path}}'", "type": "shell", "inline": [ "rpm -Uvh https://packages.microsoft.com/config/rhel/7/packages-microsoft-prod.rpm", "yum update", "yum install -y apt-transport-https", "yum update", "yum install -y aspnetcore-runtime-3.0.1", "yum install -y dotnet-sdk-3.0.1", "yum install -y curl" ] },

dagood · 2019-11-20T20:10:50Z

What are the errors, and what's the output of the commands? What type of machine is this and what Linux distro does it run?

There are some issues in general with the RPM package repos right now that might be related (#3853) but there isn't enough info here to tell yet.

dagood · 2019-11-20T23:04:34Z

Looking at this again, I don't understand how these lines could have worked before:

           "yum install -y aspnetcore-runtime-3.0.1",
           "yum install -y dotnet-sdk-3.0.1",

These packages don't exist, for a few reasons:

"3.0.1" is not an SDK version, you're looking for "3.0.101". See https://dotnet.microsoft.com/download/dotnet-core/3.0
We only create package names aspnetcore-runtime-3.0 and dotnet-sdk-3.0, the patch version isn't included. By installing one of those, you get the latest 3.0 version of that package.

If you really want to specify a specific version, the syntax to do that with an RPM package manager like yum would be yum install dotnet-sdk-3.0-3.0.101. In that case, the package name is dotnet-sdk-3.0 and its version is 3.0.101.

(Also, a side note: you don't need to install both aspnetcore-runtime and dotnet-sdk. The SDK includes the runtime.)

dpanchal-visuallease · 2019-11-20T23:52:46Z

I am using circleCI pipeline, using dotnet/core 3.0 Mostly my PC has Ubuntu 18.4 installed. docker: - image: mcr.microsoft.com/dotnet/core/sdk:3.0<http://mcr.microsoft.com/dotnet/core/sdk:3.0>

oppakjt · 2019-11-20T23:56:43Z

i have same issue.
[Info]
[root@localhost excon]# dotnet --info
.NET Core SDK(global.json 반영):
Version: 3.0.101
Commit: bc5f8df0f5

런타임 환경:
OS Name: centos
OS Version: 7
OS Platform: Linux
RID: centos.7-x64
Base Path: /usr/share/dotnet/sdk/3.0.101/

Host (useful for support):
Version: 3.0.1
Commit: 19942e7199

.NET Core SDKs installed:
2.0.0 [/usr/share/dotnet/sdk]
2.0.2 [/usr/share/dotnet/sdk]
2.0.3 [/usr/share/dotnet/sdk]
2.1.2 [/usr/share/dotnet/sdk]
2.1.3 [/usr/share/dotnet/sdk]
2.1.4 [/usr/share/dotnet/sdk]
2.1.101 [/usr/share/dotnet/sdk]
2.1.103 [/usr/share/dotnet/sdk]
2.1.104 [/usr/share/dotnet/sdk]
2.1.105 [/usr/share/dotnet/sdk]
2.1.200 [/usr/share/dotnet/sdk]
2.1.201 [/usr/share/dotnet/sdk]
2.1.202 [/usr/share/dotnet/sdk]
2.1.300-preview2-008530 [/usr/share/dotnet/sdk]
2.1.300-preview2-008533 [/usr/share/dotnet/sdk]
2.1.300-rc1-008673 [/usr/share/dotnet/sdk]
2.1.802 [/usr/share/dotnet/sdk]
2.2.402 [/usr/share/dotnet/sdk]
3.0.101 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.0-preview2-final [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.0-rc1-final [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.0-preview2-final [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.0-rc1-final [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.3 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.4 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.5 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.7 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.9 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.0-preview1-26216-03 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.0-preview2-26406-04 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.0-rc1 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.14 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.1 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

[Error]
[root@localhost excon]# dotnet run
/usr/share/dotnet/sdk/3.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(264,5): error MSB4018: "ResolveTargetingPackAssets" 작업에서 예기치 않은 오류가 발생했습니다. [/home/brandon/01.Work/excon/excon.csproj]
/usr/share/dotnet/sdk/3.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(264,5): error MSB4018: System.IO.FileNotFoundException: Could not find file '/usr/share/dotnet/packs/Microsoft.NETCore.App.Ref/3.0.0/data/FrameworkList.xml'. [/home/brandon/01.Work/excon/excon.csproj]
/usr/share/dotnet/sdk/3.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(264,5): error MSB4018: File name: '/usr/share/dotnet/packs/Microsoft.NETCore.App.Ref/3.0.0/data/FrameworkList.xml' [/home/brandon/01.Work/excon/excon.csproj]
/usr/share/dotnet/sdk/3.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(264,5): error MSB4018: at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter) [/home/brandon/01.Work/excon/excon.csproj]
/usr/share/dotnet/sdk/3.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(264,5): error MSB4018: at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode) [/home/brandon/01.Work/excon/excon.csproj]
/usr/share/dotnet/sdk/3.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(264,5): error MSB4018: at System.IO.FileStream.OpenHandle(FileMode mode, FileShare share, FileOptions options) [/home/brandon/01.Work/excon/excon.csproj]
...
...
...
...
/usr/share/dotnet/sdk/3.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(264,5): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask) [/home/brandon/01.Work/excon/excon.csproj]

mdx0111 · 2019-11-21T05:54:15Z

The same issue is happening here on Fedora 31.

The first issue which is already reported is the mismatch between the checksum of the "netstandard-targeting-pack-2.1-2.1.0-1.x86_64". I have downloaded the rpm package for that and installed it through command line.

Then I updated the .Net Core which updated the Asp.Net Core runtime and SDK as well. I have also removed all the .Net Core versions and just install version 3.0.101 through the following command:

sudo dnf install dotnet-sdk-3.0

Then I created a web app using the following command:

dotnet new web

Then in the root folder of my test project ran the following command:

dotnet build
dotnet run

Even though dotnet build runs correctly and compiles the project, dotnet run returns the following message:

It was not possible to find any compatible framework version
The specified framework 'Microsoft.AspNetCore.App', version '3.0.0' was not found.
  - No frameworks were found.

You can resolve the problem by installing the specified framework and/or SDK.

The .NET Core frameworks can be found at:
  - https://aka.ms/dotnet-download

The following shows my dotnet --info

.NET Core SDK (reflecting any global.json):
 Version:   3.0.101
 Commit:    bc5f8df0f5

Runtime Environment:
 OS Name:     fedora
 OS Version:  31
 OS Platform: Linux
 RID:         fedora.31-x64
 Base Path:   /usr/share/dotnet/sdk/3.0.101/

Host (useful for support):
  Version: 3.0.1
  Commit:  19942e7199

.NET Core SDKs installed:
  3.0.101 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.NETCore.App 3.0.1 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

The only way to get my project run is by installing ASP.NET Core Runtime 3.0.0 through the following command:

sudo dnf install aspnetcore-runtime-3.0-3.0.0-1

My dotnet --info after installing aspnetcore-runtime-3.0-3.0.0-1:

.NET Core SDK (reflecting any global.json):
 Version:   3.0.101
 Commit:    bc5f8df0f5

Runtime Environment:
 OS Name:     fedora
 OS Version:  31
 OS Platform: Linux
 RID:         fedora.31-x64
 Base Path:   /usr/share/dotnet/sdk/3.0.101/

Host (useful for support):
  Version: 3.0.1
  Commit:  19942e7199

.NET Core SDKs installed:
  3.0.101 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.0.1 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Now if I run sudo dnf update, I will get the following package update whereupon installing it I'll go back to square one.

Package                         Architecture    Version             Repository                            Size
================================================================================================================
Upgrading:
 aspnetcore-runtime-3.0          x86_64          3.0.1-1             packages-microsoft-com-prod          7.5 M

Please do not hesitate to let me know if you need any further details to investigate this.

Many thanks.

dagood · 2019-11-21T07:06:59Z

@dpanchal-visuallease I don't understand, can you please show the error and describe when it happens? Are you trying to install on your machine, some other machine, or use that Docker image?

@oppakjt That issue looks very different to me... like a corrupted install. I would suggest verifying the install, or reinstalling, then open a new issue if you have problems.

@mdx0111 That's also quite different, that's a known problem tracked by #3863.

mdx0111 · 2019-11-21T07:09:49Z

@dpanchal-visuallease I don't understand, can you please show the error and describe when it happens? Are you trying to install on your machine, some other machine, or use that Docker image?

@oppakjt That issue looks very different to me... like a corrupted install. I would suggest verifying the install, or reinstalling, then open a new issue if you have problems.

@mdx0111 That's also quite different, that's a known problem tracked by #3863.

Yes, I understand that; hence, stating that it's already reported but the rest of the information and details that I have provided are related to the issue originally reported here.

dagood · 2019-11-21T07:26:40Z

Yes, I understand that; hence, stating that it's already reported but the rest of the information and details that I have provided are related to the issue originally reported here.

I'm sorry, I'm missing how it relates to the original issue here. There isn't much to go on yet. Can you give more context why you think they're connected? I'm trying to keep this issue focused if I can.

mdx0111 · 2019-11-21T07:55:01Z

AAh! My mistake! Sorry, got confused by the title. I'll open another issue for what I'm experiencing.

Many thanks and apologies again for the confusion.

dpanchal-visuallease · 2019-11-21T14:26:25Z

Good morning, Culprit is the MIRROR, it did work once, but then it’s been failing all the times., amazon-ebs: netstandard-targeting-pack-2.1 FAILED amazon-ebs: https://packages.microsoft.com/rhel/7/prod/netstandard-targeting-pack-2.1.0-x64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=packages-microsoft-com-prod clean metadata amazon-ebs: Trying other mirror. amazon-ebs: (4/5): dotnet-sdk-3.0.101-x64.rpm Did you try installing it (dotnet-sdk-3.0.101) manually? Thanks, Dinesh

dagood · 2019-11-21T16:38:24Z

Thanks for posting the logs @dpanchal-visuallease, that is a known issue with the RPM feeds that hasn't been resolved yet: #3853.

In the meantime, you can work around this by manually installing netstandard-targeting-pack-2.1 before the SDK, ignoring the "package does not match intended download" check. Details at #3853 (comment).

dpanchal-visuallease · 2019-11-21T16:46:27Z

AWS kindly replied and it did install dotnet 3.0.101, hopefully it will fix my issue. These are the commands that worked for me: $ sudo rpm -Uvh https://packages.microsoft.com/config/rhel/7/packages-microsoft-prod.rpm $ sudo yum install dotnet-runtime-3.0 -y This installed .Net 3.0. runtime. I run these command within the Packer builder template and I was able to create a RHEL7-based AMI pre-backed with .Net 3.0 runtime. To install the .Net SDK as well, I needed to run these commands: $ sudo rpm -Uvh https://packages.microsoft.com/rhel/7/prod/netstandard-targeting-pack-2.1.0-x64.rpm # This is a required dependency that yum is unable to find in the its repositories so they need to be manually installed. $ sudo rpm -Uvh https://packages.microsoft.com/config/rhel/7/packages-microsoft-prod.rpm $ sudo yum install dotnet-runtime-3.0 -y $ sudo yum install dotnet-sdk-3.0 -y

dagood · 2019-11-21T17:09:26Z

Good to hear! That is indeed the workaround recommended at #3853 (comment), so agreed, it should work around the current problem with the linux repo.

dagood added the needs-more-info Not enough information has been provided. Please share more detail as requested. label Nov 20, 2019

mdx0111 mentioned this issue Nov 21, 2019

Missing packages for Fedora 31 #3876

Closed

dagood closed this as completed Nov 21, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

I am getting error saying package not available #3870

I am getting error saying package not available #3870

dpanchal-visuallease commented Nov 20, 2019

dagood commented Nov 20, 2019

Uh oh!

dpanchal-visuallease commented Nov 20, 2019 via email •

edited by dagood

Loading

Uh oh!

dagood commented Nov 20, 2019 •

edited

Loading

Uh oh!

dagood commented Nov 20, 2019 •

edited

Loading

Uh oh!

dpanchal-visuallease commented Nov 20, 2019 via email •

edited by dagood

Loading

Uh oh!

oppakjt commented Nov 20, 2019

Uh oh!

mdx0111 commented Nov 21, 2019 •

edited

Loading

Uh oh!

dagood commented Nov 21, 2019

Uh oh!

mdx0111 commented Nov 21, 2019

Uh oh!

dagood commented Nov 21, 2019

Uh oh!

mdx0111 commented Nov 21, 2019

Uh oh!

dpanchal-visuallease commented Nov 21, 2019 via email •

edited by dagood

Loading

Uh oh!

dagood commented Nov 21, 2019

Uh oh!

dpanchal-visuallease commented Nov 21, 2019 via email •

edited by dagood

Loading

Uh oh!

dagood commented Nov 21, 2019

Uh oh!

I am getting error saying package not available #3870

I am getting error saying package not available #3870

Comments

dpanchal-visuallease commented Nov 20, 2019

dagood commented Nov 20, 2019

Uh oh!

dpanchal-visuallease commented Nov 20, 2019 via email • edited by dagood Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dagood commented Nov 20, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dagood commented Nov 20, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dpanchal-visuallease commented Nov 20, 2019 via email • edited by dagood Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

oppakjt commented Nov 20, 2019

Uh oh!

mdx0111 commented Nov 21, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dagood commented Nov 21, 2019

Uh oh!

mdx0111 commented Nov 21, 2019

Uh oh!

dagood commented Nov 21, 2019

Uh oh!

mdx0111 commented Nov 21, 2019

Uh oh!

dpanchal-visuallease commented Nov 21, 2019 via email • edited by dagood Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dagood commented Nov 21, 2019

Uh oh!

dpanchal-visuallease commented Nov 21, 2019 via email • edited by dagood Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dagood commented Nov 21, 2019

Uh oh!

dpanchal-visuallease commented Nov 20, 2019 via email •

edited by dagood

Loading

dagood commented Nov 20, 2019 •

edited

Loading

dagood commented Nov 20, 2019 •

edited

Loading

dpanchal-visuallease commented Nov 20, 2019 via email •

edited by dagood

Loading

mdx0111 commented Nov 21, 2019 •

edited

Loading

dpanchal-visuallease commented Nov 21, 2019 via email •

edited by dagood

Loading

dpanchal-visuallease commented Nov 21, 2019 via email •

edited by dagood

Loading