I think we missed forwarding the proxy setting to aptdaemon when update-
manager switched to that. That said, aptdaemon's proxy support is even
more rudimentary than update-manager's: It only supports one proxy.
update-manager at least has http and https proxies; apt itself supports
proxies configured per host.
Regarding init_proxy():
1. The init_proxy() method initializes the http{s,}_proxy variables from
apt.conf files, if there are any. So it does not need to check the
variable, as it writes it if needed (now, what should take precedence -
general proxy settings or package manager proxy settings is an entirely
different topic!)
2. update-manager's reading of synaptic.conf is irrelevant, it's old
legacy code.
3. update-manager has no way of configuring a proxy other than apt.conf
entries. If you are talking about your user (gnome) preferences, then
those affect your user session, not package management.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777428
Title:
UpdateManager does not work behind proxy in many cases
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1777428/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
