vscode: Failed to fetch due to Hash sum mismatch
When I was trying to update, I got the Hash sum mismatch error on terminal.
- VSCode Version:1.40.2
- OS Version:Ubuntu LTS 18.04 (Linux x64 5.0.0-37-generic)
Steps to Reproduce:
1.sudo apt update at terminal 2.Get the following error log
E: Failed to fetch http://packages.microsoft.com/repos/vscode/dists/stable/main/binary-amd64/Packages.bz2 File has unexpected size (156056 != 156065). Mirror sync in progress? [IP: 10.77.8.70 8080]
Hashes of expected file:
- Filesize:156065 [weak]
- SHA512:12e6dffcd247d1ff067acfa61a3c4eb6078c326c2858feb4f6f141a1d809e22292a78282414a5c103038ea80bb63cd734c7516782c9809c341335083d4e7611b
- SHA256:c850f35f1979831ac75641978c397e51519fa22313598ec12bde5f52277044c0
- SHA1:1f65f4a7388c22bcf7b7f30fb7bc337c60d94b2e [weak]
- MD5Sum:4153a12e4a5629bfb14ed98f4c8ac234 [weak]
Release file created at: Thu, 12 Dec 2019 19:59:19 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.
Previously:
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 81
- Comments: 93 (5 by maintainers)
@rpellerin Maybe not. It does increase the noise, I agree, but it’s a great metric of how pervasive the problem is. Unless we have a voting/input system of sorts (“Yes, I have this problem, too!”), the number and intensity of comments is the only way 😃
Ok maybe people should stop posting messages such as “Same on <platform>”. I guess at this point they know most (if not all) Debian-based distros are affected.
Also seeing this, same version of VSCode and Ubuntu as OP.
In #41094 (almost 2 years ago), @Tyriar said “the team is planning on putting together better monitoring to hopefully catch this sort of thing earlier.”
Apparently whatever was planned didn’t go so well? Maybe some automation is needed?
I’ve contacted the linux repo team about this and am waiting for them to resolve it.
I love all the people chiming in with “I’m having the same issue on [distro] v[XX.xx] [desktop environment] as well!” Yes, you’re all going to have the issue. The vscode team screwed up their PGP key. It’s not going to work for any of us until they fix the key. It will probably be resolved by tomorrow, because it’s not that difficult of a fix. So just manually ignore the vscode update until it’s fixed. If you don’t know how to do that, read this
Edit: Here’s a more comprehensive guide to ignoring repos, if you’re interested. https://www.tecmint.com/disable-lock-blacklist-package-updates-ubuntu-debian-apt/
And oh, I’m too having this problem with Xubuntu 18.04. 😆
Fixed 😃
https://en.wikipedia.org/wiki/Friday_the_13th 😄
Same 19.10
I’ve the same issue on Ubuntu 18.04.3 and 16.04.6 LTS.
Same here. Ubuntu 18.04.3.
$ software-properties-gtk -> other software window -> remove Microsoft link $ sudo apt-get update
FYI for a little more transparency, this happened because changes were pushed to the system that drives https://packages.microsoft.com/ (for the majority of MS Linux offerings) and they caused issues with metadata sync. We have similar issues periodically where some repo files don’t regenerate without their team doing some manual intervention. Unfortunately all we (the VS Code team) can do is ping them when things go wrong and hope that the underlying problems get fixed eventually.
Same with Ubuntu 16.04
It seems the signed release file http://packages.microsoft.com/repos/vscode/dists/stable/InRelease (InRelease) is old and does not match the files on the repo.
For all people trying to help by saying “remove the vscode.list file” don’t forget, the issue created here is a vscode (Microsoft (as it applies to dotnet-core as well)) issue, not an apt issue, and removing the .list file will only allow us to update all other packages, vscode won’t be updated unless the vscode.list file exists and works. (Yes I know we can install the update using the .deb, but that is not the issue here either)
Yeah, I am absolutely clear what the problem is, but also know how to solve it. But I still come here and write down “Same on …”. This is just a euphemism to express: “Hey, you guys screwed up again.” Yeah, again and again. You guys represent a great software company. Don’t let me so dispoint. Just setup an automated test please.
Reporting in with the same issue. Ubuntu 18.04.3
Ditto. Ubuntu 18.04.
same thing here Linux Mint 19.2 Cinnamon
Same here, Ubuntu 19.10
At least people should look for duplicates and thumb up messages mentioning their own distro instead of re-posting.
It is everywhere now 😃… I have removed the vscode sources for now until this is fixed.
sudo rm /etc/apt/sources.list.d/vscode.list
Was with the same problem, apparently normalized.
Looks like this might be fixed
I receive the exact error in Linux Mint 19.2 Tina
Same error with Linux Mint 19.1 Tessa
mint 19.2
Debian 10
Simply remove removed the vscode sources for now and add when it is fixed. sudo rm /etc/apt/sources.list.d/vscode.list
dotnet core is affected too by this fuck up: dotnet/core#3988
Ubuntu 18.04 x64:
Also having the same issues installing msodbcsql17 on debian buster
Same problem on Elementary OS 5.1
Earlier from @RMacfarlane:
Pinging @sbatten as endgame master for this release. This seems to be taking a long time to resolve, and is resulting in a lot of dup issues. The bot isn’t doing a great job of spotting them either.
Same error occurring during update on Ubuntu 18.04.
`Err:11 http://packages.microsoft.com/repos/vscode stable/main amd64 Packages
File has unexpected size (156354 != 156065). Mirror sync in progress? [IP: 13.76.190.189 80] Hashes of expected file:
Same here 😦 Ubuntu 18.04
Same problem with Linux Mint 19.
https://packages.microsoft.com/repos/vscode/dists/stable/InRelease https://packages.microsoft.com/repos/vscode/dists/stable/Release In these files values changed for
That’s probably why there are hash sum mismatches.
Ubuntu 19.10 here, however, I updated successfully within 30 minutes of the 1.41 release on my work PC which is also Ubuntu 19.10. getting the error now on my laptop. (Was able to install using the
.deb
. but still can’t update usingapt
)I am getting the issue for the dotnet core apt repo as well, so it might be microsofts servers…