-
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
Ubuntu 18.04 (Bionic) MS repo contains hash mismatches #5860
Comments
This package is unrelated to .NET and I'm not familiar with it--it would be ideal if you can report this to whoever maintains that package so they are alerted to the problem and can get the packages.microsoft.com team to fix it. That said, if we can help (@rbhanda), the next piece of info we need is which mirror you're hitting. @ogreenz Can you provide the full output of one of these commands (in particular to get the IP)? |
Sure here's the output I'm getting:
|
Thanks, that looks like the right info. I still think you should try contacting support for that package (SQL Server, Azure?) in case we're not able to help. |
Hi @ogreenz I checked with our packages.microsoft.com team and they are not able to repro this issue including the mirror. They are suggesting to try to clear the cache and retry to see if that works. |
Hi @rbhanda I don't think it's a cache issue. I just tried this from a US server and got the following address:
The exact same issue is happening there too. you can just download these files and see for yourself:
the relevant package is defined in line 918 in the Packages file, in it you could see the MD5 is: while the downloaded file has the md5 hash of: This is from 2 separate instances of the same repo now. |
Hi @ogreenz I followed up on this with our internal team but they were not able to repro this . Are you still seeing this issue? |
Hi @rbhanda, yes downloading the files again yield the exact same result.
and getting MD5 of I think it's pretty binary either they are the same hash or they aren't. |
Thanks for reporting @ogreenz . Since this package is not owned by .NET, I am not sure how else I can help here. Are you able to contact support for this package as suggested
|
It looks like the latest version of the package isn't affected, only the old one. (I don't have insight into what the packages.microsoft.com team did to try but fail to repro the problem, though.) Here's a simple repro using Docker for a fresh start:
This might be useful for a report to SQL/Azure to narrow it down. |
Hi @rbhanda, the package isn't owned by .NET but this repo is where you update .NET core from, and it's broken. |
@dagood I downloaded the file manually and checked the hash against the one in the Packages file and there is indeed a mismatch |
@teottin, can you please file a new issue for that package and/or report the problem to whoever pointed you at that package? |
@dagood It seems the problem has been resolved now, I guess someone resposible for packages.microsoft.com updated the pacakge index. |
Not as far as I know (unfortunately). In my experience, the team that maintains packages.microsoft.com defers a lot of responsibility onto the individual product teams that push packages into it. However, I don't work in this area anymore--the best way to get your issue routed correctly is to file a new issue. The team wasn't able to repro the original issue in this thread (even though I was able to), but maybe with a new package/report they would have been able to repro and fix it proactively. What might have happened in this case is that another version of the package happened to be published, which regenerated the index without anyone really being aware of this problem. Whether or not we're able to recommend mirroring the repo is still up in the air: #2882. (I assume it's fine, but I don't know about the licenses of every package potentially being redistributed.) |
While I was trying to sync my repository from
https://packages.microsoft.com/ubuntu/18.04/prod
it seemed to fail because there are md5 hash mismatches.Error message:
The file
https://packages.microsoft.com/ubuntu/18.04/prod/dists/bionic/main/binary-amd64/Packages
was changed at January 16th, 2020, and seems to contains now a wrong hash. I was able to sync a week ago.I also was able to confirm it manually by downloading the file, compute the hash, and compare it to the one found inside the "Packages" file.
Solution:
The "Packages" file in the mirror needs to be re-generated.
Please let me know if you need any more information.
I'm cc'ing @dagood because I saw you've handled a similar issues #3988 & #2608 in the past.
Best,
Ofir.
The text was updated successfully, but these errors were encountered: