Bug#703422: Use bracket notation or full URI notation when printing IPv6 addresses
Package: apt
Version: 0.9.7.8
Severity: wishlist
Hi,
I was recently helping to debug an issue with APT (which turned out to
be just left-over IPv6 proxy configuration) and I have noticed that
the APT output prints raw IPv6 addresses without brackets which is
very confusing.
Err http://ftp.cz.debian.org unstable Release.gpg
Could not connect to 2001:db8::ff00:42:8329:8049 (2001:db8::ff00:42:8329). - connect (110: Connection timed out)
Would it be possible either to use bracket form, e.g.:
Could not connect to [2001:db8::ff00:42:8329]:8049 (2001:db8::ff00:42:8329). - connect (110: Connection timed out)
Or (which might be better and easier since it doesn't require any
address-or-ipv6-address detection) use full URI as specified in the
Acquire::http::Proxy directive, e.g.:
Could not connect to http://[2001:db8::ff00:42:8329]:8049 (2001:db8::ff00:42:8329). - connect (110: Connection timed out)
It would really help the debugging.
Also it might be a good idea to say something about proxy unavailable - (that's not IPv6 specific), e.g.:
Could not connect to proxy http://[2001:db8::ff00:42:8329]:8049 (2001:db8::ff00:42:8329). - connect (110: Connection timed out)
Thanks for considering this in the future,
Ondrej
-- Package-specific info:
-- (/etc/apt/preferences present, but not submitted) --
-- (/etc/apt/sources.list present, but not submitted) --
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apt depends on:
ii debian-archive-keyring 2012.4
ii gnupg 1.4.12-7
ii libapt-pkg4.12 0.9.7.8
ii libc6 2.13-38
ii libgcc1 1:4.7.2-5
ii libstdc++6 4.7.2-5
apt recommends no packages.
Versions of packages apt suggests:
pn apt-doc <none>
ii aptitude 0.6.8.2-1
ii dpkg-dev 1.16.9
ii python-apt 0.8.8.1
ii xz-utils 5.1.1alpha+20120614-2
-- no debconf information
Reply to: