Bugzilla Bug 31798

I did emerge -uD world this morning and there was an upgrade to wget-1.9.

After that, emerge could not download any more. The error message thrown by wget is "failed: Address family not supported by protocol."
In a chat session, someone adviced me to re-emerge wget that would solve the problem. But it didn't.

Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r6, 2.4.23-pre7)
=================================================================
System uname: 2.4.23-pre7 i686 Intel(R) Pentium(R) M processor 1300MHz
Gentoo Base System version 1.4.3.11
distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=pentium3 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O3 -march=pentium3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="sandbox ccache autoaddcvs"
GENTOO_MIRRORS="http://192.168.30.3/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 foomaticdb libg++ mad mikmod xml2 xv zlib directfb gtkhtml gdbm berkdb slang readline svga guile sdl gpm tcpd pam libwww ssl esd imlib motif opengl dga ggi plotutils xml gd -3dnow -apm -arts alsa hbci X ipv6 gtk gnome oss tcltk gtk2 kde aalib acpi apache2 avi bonobo cdr crypt cups dvd encode fbcon gif jpeg tiff png -java mozilla mmx maildir mbox ncurses nls cardbus oggvorbis mpeg pdflib perl python qt quicktime samba scanner spell sse tetex truetype usb xface xmms mysql mozsvg mozcalendar gnomedb dv"

I confirm this. No matter what protocol or what address, the outcome is always
the same:

# wget http://www.gentoo.org/main/en/about.xml
--10:44:38--  http://www.gentoo.org/main/en/about.xml
           => `about.xml'
Resolving www.gentoo.org... 203.112.31.164, 212.162.48.146, 195.66.242.4
Connecting to www.gentoo.org[203.112.31.164]:80... failed: Address family
not supported by protocol.
Connecting to www.gentoo.org[212.162.48.146]:80... failed: Address family
not supported by protocol.
Connecting to www.gentoo.org[195.66.242.4]:80... failed: Address family not
supported by protocol.
Retrying.



# wget ftp://ftp.kernel.org/pub/README
--10:45:56--  ftp://ftp.kernel.org/pub/README
           => `README'
Resolving ftp.kernel.org... 204.152.189.116
Connecting to ftp.kernel.org[204.152.189.116]:21... failed: Address family
not supported by protocol.
Retrying.

A workaround is to emerge wget with -ipv6. The problem is only there when
ipv6 is in $USE.

I'd like to confirm this behavior.  wget does not work with USE=ipv6 turned
on, but does work with USE=-ipv6 set.

I can confirm this bug!

Please see http://www.episec.com/people/edelkind/patches/ for a dual-family
patch for wget 1.9.  I have submitted this patch to the wget-patches list
as well.

Have same problem, emerging with -ipv6 worked.

Try again compiling wget with ipv6 support after loading ipv6 kernel module
(wasn't loaded by default) and after that, also wget worked.

People that have problems with it should check if ipv6 kernel support was
compiled as a module and in that case, check if you are loading it or not.

You're right, I did'nt had any ipv6 kernel modules loaded. But regardless
wget should'nt break then. Older wget versions work even without ipv6 kernel
support. This breakage is new and was introduced with version 1.9.

seemant: you bumped the version on wget, please fix it!
use the dual family patches that the one person here posted.

committed wget-1.9-r1 with ari's patch. sorry for the inconvenience, everyone.

wget-1.9.1-r2 as well as wget-1.9.1-r1 fail to download.
my USE flag contains "-ipv6"
the only way I get could wget to work again is by either not applying the ipvmisc patch or by adding
myconf="${myconf} --with-ipv4-default"
to the ebuild. is there a chance that the ebuild be made to configures "--with-ipv4-default" when -ipv6 is specified, or a least enable the user to set "--with-ipv4-default" without having to edit the ebuild every time?
TIA