Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

http://bugs.gentoo.org/show_bug.cgi?id=315977 https://bugzilla.novell.com/show_bug.cgi?id=597616 https://qa.mandriva.com/show_bug.cgi?id=58834 Best regards, -- Tore Anderson -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas

Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

the behaviour that will serve end users the best. Best regards, -- Tore Anderson -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bc98304.2010...@fud.no

Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

, -- Tore Anderson --- glibc-2.11-332-g2e7c805/ChangeLog +++ glibc-2.11.90-17/ChangeLog @@ -1,3 +1,9 @@ +2010-04-06 Ulrich Drepper drep...@redhat.com + + * sysdeps/posix/getaddrinfo.c (default_scopes): Assign global + scope to RFC 1918 addresses. + * posix/gai.conf: Document difference

Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

fixed ASAP. I therefore hope that Debian can help out by implementing the suggested change, either by shipping the /etc/gai.conf file by default, or by modifying the getaddrinfo.c sources, so that RFC 1918-based addresses are treated as globally scoped by default. Best regards, -- Tore Anderson

Bug#204654: glibc 2.3.2-2 breaks apache on ia64

the nonstripped Apache binary, then upgraded again? I think you should be able to get a useful backtrace then. -- Tore Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]