Hello, I am not familiar about the release process, so I do not know how could I grab a fixed apt and install it to confirm this fixes my original issue.
I went without updating these VMs quite for some time (vacations!), but now can re-test if that helps. Thanks for checking and providing a fix for the issue. Regards, ///Pablo 2016-11-13 20:53 GMT-03:00 Pablo Di Noto <[email protected]>: > > (mhh, I wonder why I missed the initial report…) >> > > Not familiar with Debian bug system, so perhaps I did not follow the > proper procedure? > > >> >> On Sun, Nov 13, 2016 at 08:15:57PM +0100, Markus Wanner wrote: >> > > Acquire::http::Proxy "http://10.137.255.254:8082/";; >> > >> > Out of curiosity and hopefully narrowing down the issue: What kind of >> > proxy is this on your side? >> >> Another good point would be running apt with: >> -o Debug::pkgAcquire::Worker=1 -o Debug::Acquire::http=1 >> > > Will try this during the week, once the downloaded files get expired. > > >> And is "repeatedly" meant to refer to "reproducible all the time" or >> "happens often, but no obvious pattern"? >> > > The pattern I was able to detect is that: > - It always happen on files related to dep11 and icons, which are quite > big. > - Happens 50% of the time > - Happens on debian 8 and debian 9 (will collect same set of logs on the > newer template) > > >> Interesting is the failure in copy ("E: Failed to fetch copy:") as that >> is supposed to "just" move files around without (un)compression – and we >> have passed the stage proxies could interfere as the download itself >> verified (or not, maybe it IMS hits in some way and copy is supposed to >> verify it – there are various ways such a not-modified state can be >> reached and proxies are notoriously bad with it…). >> >> btw: It is best to run apt with the least amount of config usually. The >> mentioned config options are rather special case and especially the >> "Acquire::BrokenProxy" one doesn't even exist… (I looked once, it seems >> to have existed ~10 years ago for one year in no stable release and the >> name was very bad for what it actually did…). Rule of thumb: If you >> don't know what you are doing, use neither – unfortunately it seems the >> people commonly answering questions on q&a-sites tend to be in the very >> vocal "no idea, but I get points for posting stuff anyhow" group. >> > > Now that I realize the proxy is a suspect, I will clone the template and > perform the same update with and without the proxy. That should provide > some clues. Same goes for the "bare minimum" apt-config file. > >> > Thanks for the suggestions, > ///Pablo >
