Bug#611891: Half configured ipv6
On 03/21/13 16:27, Michael Vogt wrote:
> On Thu, Mar 21, 2013 at 10:19:57AM +0000, Dick Middleton wrote:
>> Hi,
>> I've been hit by this as well. For example RaspberryPi.org and their
>> repositories at raspbian.org have AAAA records in DNS but these addresses are
>> broken i.e. return nothing. This is going to happen more often as sites
>> experiment with ipv6. Ideally programs should fall-back gracefully to ipv4 if
>> ipv6 is not working.
>
> The attached patch should make this work:
> $ sudo apt-get install --force-ipv6 2vcard
> or
> $ sudo apt-get install 2vcard -o Acquire::ForceIPv4=true
>
> I guess the open question is if we want a commandline switch or just a
> config option and if "Acquire::ForceIPv{4,6}" is a good name.
Personally I think a config option is more useful. FWIW I did discover this
morning that apt-cacher-ng has something similar:
acng.conf
# Specifies the IP protocol families to use for remote connections. Order does
# matter, first specified are considered first. Possible combinations:
# v6 v4
# v4 v6
# v6
# v4
# (empty or not set: use system default)
#
ConnectProto: v4 v6
However I don't think that apt-cacher falls back either if is there is no
response from ipv6 server. That would be best; we don't really want to force
things back on to ipv4 just because some ipv6 servers are broken.
The OP has a different issue of course.
Dick
--
Dick Middleton
dick@lingbrae.com
Reply to: