Bug#37411: apt: apt now (unsuccessfully) tries to resolve IP addresses when http_proxy is set with an IP address.
Package: apt
Version: 0.3.4
The libc6 package seems to be involved.
I always used this proxy setting with apt without problem:
export http_proxy=http://192.168.1.1:3128/
Now I get this error when typing for example: apt-get update
[...]
Err http://nonus.debian.org potato/non-US Packages
Could not resolve '192.168.1.1'
Err http://nonus.debian.org potato/non-US Release
Could not resolve '192.168.1.1'
Err http://www.debian.org unstable/main Packages
Could not resolve '192.168.1.1'
Err http://www.debian.org unstable/main Release
Could not resolve '192.168.1.1'
[...]
lynx is using http_proxy too and handles IP addresses without problem
(ie the same http_proxy=http://192.168.1.1:3128/ )
ii lynx-ssl 2.8.1-1 Text-mode WWW Browser supporting SSL
If I put in http_proxy some address from /etc/hosts or DNS,
apt-get works again.
I'd like apt returns to its old behavior allowing both IP and resolved
addresses in proxy settings.
Since apt hasn't been changed since Sun, 4 Apr 1999 18:26:44 -0500,
libstdc++2.9 since Sat, 20 Feb 1999 22:06:21 +0100
and since libc6 was changed Fri, 7 May 1999 10:40:11 -0700
according to changelogs, and that last week all was fine with ip
addresses, I have to conclude that it's a change in libc6 that created
this bug. Anyways I'm sure a change in apt can correct this.
-- System Information
Debian Release: potato
Kernel Version: Linux blackhole 2.2.7-ac3 #1 sam mai 8 18:15:34 EDT 1999 i586 unknown
Versions of the packages apt depends on:
ii libc6 2.1.1-3 GNU C Library: Shared libraries and timezone
ii libstdc++2.9 2.91.61-1 The GNU stdc++ library (egcs version)
Reply to: