-
Notifications
You must be signed in to change notification settings - Fork 4.9k
CentOS, Fedora, openSUSE, RHEL error "checksum doesn't match" "Package does not match intended download" "Digest verification failed" #3853
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
Comments
+1 |
If you look at https://packages.microsoft.com/centos/7/prod/repodata/, you see that On the other hand, looking at https://packages.microsoft.com/centos/7/prod/, you can see that So it's quite likely that |
If you're really sure the netstandard-targeting-pack-2.1.0-x64.rpm on the Microsoft repo is correct, you can work around this issue like this:
|
I'm sending a mail to the Linux repo admins to see what's going on here. This kind of thing has happened in the past due to the service not syncing properly, only updating the RPM or only updating the checksums. The line in those logs that really shows what this is is this one, by the way:
(Big thanks for the complete logs!) |
@dagood is the Linux release process open sourced? |
Unfortunately not, and visibility (even mine) is very limited. |
ok, that's a shame 😞 . hope this gets fixed soon, it's blocking system upgrades. As far as I can tell if I remove this package, I won't be able to reinstall it(!) |
@qmfrederik's workaround seems like it will work as a short-term workaround. The packages themselves are signed, so we know that the integrity at least is ok.
The Linux repo admins do tend to respond to direct problems like this fairly quickly, so hopefully this will be resolved soon (today). |
This definitely also affects |
The Linux repo admins have tried to regenerate the filelists to fix this problem. It didn't work for me, but it might be worth retrying in case it's somehow on my end. They're continuing to look at the problem. I don't have an ETA yet but I will update once I hear more. |
There are still issues netstandard-targeting-pack-2.1 FAILED ======== ] 12 MB/s | 82 MB 00:00:02 ETA https://packages.microsoft.com/centos/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 Error downloading packages: |
@qmfrederik I try your way, it works, thx! |
This also affects openSUSE, blocking system upgrades:
|
Are there any plans in the roadmap to open-source the release pipeline? The community can't help resolve this / maintain ongoing changes e.g. #3876 when it's proprietary. |
Given this completely blocks system updates/upgrades for stable users across multiple distributions, can we get some update on this? To echo @craigjbass : can we get some level of transparency around this? Everything's closed, we have no direct comms to the team and bugs like this are breaking people's systems. |
I can't speak for Microsoft, but one common approach used by many open source projects is that the Linux distribution community itself takes care of maintaining and packaging projects for their own distribution. If that path sounds appealing to you, please get involved in https://github.com/dotnet/source-build/ and packaging for your favourite distribution. |
The Linux repo admins are able to repro the issue but are having trouble figuring it out. I pointed out the checksum issue more concretely to them last night (~15hr ago) and I'll update here once I get a response.
This is the way forward IMO. I'm not aware of any plans to make the Microsoft linux repo publishing tools or service open. The only transparency improvement I'm aware of is a plan to put a service health status page online. I don't know any ETA for this. (And yeah, it doesn't seem helpful in this situation because the repo is online, but invalid.) |
Now there is a new dependency gaffe - when I run the following (from cent7 dockerfile):
I am getting the following:
Looks like the dependency management is messed up - that URL refers to a resource that does not exist. |
This looks like a repro of #3875 (RHEL 7) on a new platform (CentOS 7), noting it over there. |
The Linux repo admins have fixed this for CentOS 7, but not Fedora, openSUSE, or RHEL yet. Still working on it. |
The admins determined we might be able to fix this by deleting and reuploading the affected packages ourselves. @leecow is working on it. |
@dagood And when package netstandard-targeting-pack-2.1.0-x64.rpm for Fedora 30 will be resigned ? |
The delete + reupload is about forcing the repos to purge some old bad checksums they are currently storing, there is no problem with signing. I don't have any ETA, @leecow may be able to give an update. |
Cleared up some permissions problems and working my way through the rpm repos now. |
I used to have the checksum problem. Now I'm facing a new problem: sudo dnf install dotnet-sdk-3.0
|
@castelobranco - I'm running through the re-uploads now. |
This should be resolved for all rpm repos now. Sorry that took so long! |
@leecow This problem has appeared to have re-emergerd sometime yesterday. Got the following when building a Docker image with
|
Works beautifully when I switch to the RHEL7 RPMs. |
@yoshiya8 I don't hit the issue on a fresh CentOS 7 container, this works fine for me (your commands +
|
That is interesting - I cannot run the same thing exactly because we are behind a proxy with SSL packet inspection... I will see if I can get something similar going. |
@dagood - This is very interesting that worked beautifully with my base container. Now I just need to figure out why this recipe is not working in my Docker build... |
I'm seeing @leecow said the repo is updated everywhere but I just tried the same steps as in the "steps to reproduce this issue" and got the same failure. I am running centos 7 as a virtual server on aws EC2 that I just spun up today. I did not think to run "yum update" prior to attempting to install, but I doubt that would have anything to do with the issue. I ended up using the "install -y" command shown in the replies above to get it to install. |
Yeah, I wouldn't expect this to make a difference. @DedicatedManagers in a new issue, can you please post your log (especially the error lines) and commands that you ran? What is the The only reason I can imagine you'd hit it now is some weird caching or proxy issue. We've verified that as far as we're able to repro, this was broken before and fixed now. |
@dagood I'll be spinning up another server in a week or so and will report back if the issue is still there then. |
Just occurred to me as well:
|
Occurring for me as of today on Amazon Linux 2 using the CentOS 7 repo. Was working fine yesterday.
|
@thecosmicfrog I'm unable to repro--I suggest the same as above: in a new issue, can you please post your log and commands that you ran? What is the |
Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/install
Operating System: linux
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
Steps to reproduce this issue
Error detail
What I tried
Related issues
#3756
#3747
The text was updated successfully, but these errors were encountered: