Whether this works in all cases or not, I don't know. However, from an advocacy standpoint, regardless of who or what is at fault, it's a bad thing, probably frightening to newcomers.
Perhaps ensuring that a message along with it would solve the problem. As it is, it's cryptic, giving no indication that it's a minor issue that will probably disappear in an hour Something along the lines of, after the error message, please try running sudo apt-get update -o Acquire::http::No-Cache=true, then run apt-get update again would be an explanation that newcomers can understand, one that would probably fix the issue, which will probably continue, since it often just seems to be a minor glitch, and not scare people off.
This still exists. As mentioned in the duplicate https:/ /bugs.launchpad .net/ubuntu/ +source/ apt/+bug/ 24234
it's been an issue for 5 years.
The fix that works for me is stated by Geoff in the other bug
sudo apt-get update -o Acquire: :http:: No-Cache= true
Whether this works in all cases or not, I don't know. However, from an advocacy standpoint, regardless of who or what is at fault, it's a bad thing, probably frightening to newcomers.
Perhaps ensuring that a message along with it would solve the problem. As it is, it's cryptic, giving no indication that it's a minor issue that will probably disappear in an hour Something along the lines of, after the error message, please try running sudo apt-get update -o Acquire: :http:: No-Cache= true, then run apt-get update again would be an explanation that newcomers can understand, one that would probably fix the issue, which will probably continue, since it often just seems to be a minor glitch, and not scare people off.