Hi On Sat, Aug 31, 2019 at 01:40:10PM +0000, southernt...@thunix.net wrote: > Package: auto-apt-proxy > Version: 11 > > auto-apt-proxy should timeout earlier when the local apt cache is not > reachable. It took several minutes before acknowledging the proxy was > unavailable: > > > root@laptop:/home/user# time apt update > > Hit:1 http://security.debian.org/debian-security buster/updates InRelease > > Hit:2 http://packages.microsoft.com/repos/vscode stable InRelease > > Get:3 http://debian.mirrors.ovh.net/debian buster InRelease [118 kB] > > Get:4 http://debian.mirrors.ovh.net/debian buster-updates InRelease [49.3 > > kB] > > Get:5 http://debian.mirrors.ovh.net/debian buster-backports InRelease > > Fetched 214 kB in 3s (81.4 kB/s) > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > 1 package can be upgraded. Run 'apt list --upgradable' to see it. > > > > real 7m40.237s > > user 0m2.930s > > sys 0m0.723s > > Given auto-apt-proxy is mostly useful in a LAN context, it should time > out after seconds, not minutes. Obviously, fetching a package can take > time, but simply querying the proxy should succeed or fail > quasi-instantly.
Can you give me a hint how can one reproduce this issue? what was exactly the state of your proxy to cause this?
signature.asc
Description: PGP signature
