apt cant work with disable proxy
Bug #47044 reported by
marian
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Debian) |
Fix Released
|
Unknown
|
|||
apt (Ubuntu) |
Fix Released
|
Medium
|
Michael Vogt | ||
Dapper |
Fix Released
|
Medium
|
Michael Vogt | ||
apt-setup (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Dapper |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apt
in my apt.conf is a proxy-entry
on a other place (proxy is not unknow on this place), i disable this.
in the apt.conf is the entry "Acquire::::Proxy "false";".
the problem: is only work, if deleted this entry.
TEST CASE:
1. ensure that the apt.conf contains "Acquire:
2. run sudo apt-get update -o Debug::
3. notice that all GET requests start with a http:// - this is wrong
4. install the version from dapper-proposed
5. run sudo apt-get update -o Debug::
6. verify that all GET requests start with "/" now (no http:// anymore)
Changed in apt: | |
status: | Unknown → Fix Released |
Changed in apt: | |
status: | In Progress → Fix Committed |
description: | updated |
To post a comment you must log in.
I had a similar issue with a Dapper Drake install. In my /etc/apt/apt.conf, the installation process placed 'Acquire: :http:: Proxy "false";' This meant apt could not connect to anything, since the proxy "false" didn't exist. Removing the entry allowed apt to access all repositories.
The only oddity I can think of during my initial installation was networking. The computer is a laptop with a wireless and wired connections available. The wireless went to a dead end network that needs a VPN to get out of (much more secure than WEP that way). Anyway, when the gnome environment came up, it initially wasn't able to access the net until I had manually removed the wireless from the routing table. Perhaps something assumed that some sort of proxy was needed, but I didn't enter one?