Hash sum mismatches with apt about pac4cli HOT 5 CLOSED

I've had success with:

$ cat /etc/apt/apt.conf.d/80http 
Acquire::http::No-Cache true;
Acquire::http::Pipeline-Depth 0;

for this sort of thing in the past.

from pac4cli.

This probably has the same root cause as #13 , and I like @eythian's suggestion. Wikipedia says that on http < v2, http pipelining is barely used and often not properly implemented. That's probably also true for the monkey-patched twisted code that pac4cli uses.

In general, pac4cli's http handling is poorly tested because most traffic goes over https (so proxy CONNECT) these days. That also means that I haven't dared put the proxy configuration for Apt in the debian package. (Another reason for that is that it would mean a pac4cli breakage means we can't update pac4cli to fix it.)

from pac4cli.

as an addendum, it seems that the Acquire::http::No-Cache true; directive is unnecessary (I'll amend this comment if reality proves me wrong).

from pac4cli.

from pac4cli.

-> #37

from pac4cli.