Had to wait since yesterday myself, just stay calm, to me it seems that the apt-mirrors need longer to update themselves as intended right now…
Try again later, It’ll work!
We are suffering persistent mirror replication issues, so I have now fallen back to a single mirror. Updates will be significantly slower, but will consistently work.
This is not a sign of error with your device, but due to high reports of this error (and confusion amongst users) we have now disabled mirrordirection so users do not think something is wrong.
There existed an issue where updating within a 2-3 minute timeframe from a push could cause a Hash Sum Mismatch error. We have now addressed this, although downloads and updates will now be much slower until it is dealt with properly.
Last modification reported: Sun, 16 Feb 2020 12:37:09 +0000*
Release file created at: Tue, 24 Mar 2020 22:00:57 +0000* E: Some index files failed to download. They have been ignored, or old ones used instead.
Eventually it resolves, but I am still keen to understand why do I need to wait days, even a week for this to eventually get fixed?
(I had to break https manually because “new users can have max 5 links in a post ”)
How? I have tested from my own W10 notebook: (WSL Ubuntu)
sape@X1G7:~$ curl http://103.1.138.206/ftp.fau.de/osmc/osmc/apt/dists/stretch/main/binary-armhf/Packages.gz --output Packages.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 24817 100 24817 0 0 932k 0 --:–:-- --:–:-- --:–:-- 969k
sape@X1G7:~$ sha256sum Packages.gz
065771950f0ff6a11fa74ff98d8eb9e8ff73b884d8e09f170518ac630c4366e0 Packages.gz
a.k.a. the wrong SHA256 this way too
Hmm, having switched over to wifi from my mobile hotspot:
sape@X1G7:~$ wget -qO- ftp.fau.de/osmc/osmc/apt/dists/stretch/main/binary-armhf/Packages.gz | sha256sum
065771950f0ff6a11fa74ff98d8eb9e8ff73b884d8e09f170518ac630c4366e0 -
sape@X1G7:~$ wget -qO- ftp.fau.de/osmc/osmc/apt/dists/stretch/main/binary-armhf/Packages.gz | sha256sum
447888d9faa915906a22471c0add1bd8770493cfd911502eb658fa3c91697f5c -
sape@X1G7:~$
So the only questions is how can I get around of this transparent proxy? Should not work for HTTPS right (they cannoy fake the cert for your domain)?