Processed: Re: libc6: resolving: does not try different nameserver after "recursion not available"

Processing commands for cont...@bugs.debian.org: > # I can still reproduce it. > tags 632273 = moreinfo Bug #632273 [libc6] libc6: resolving: does not try different nameserver after "recursion not available" Added tag(s) moreinfo; removed tag(s) unreproducible. > quit Stopping processing here. P

Bug#632273: libc6: resolving: does not try different nameserver after "recursion not available"

# I can still reproduce it. tags 632273 = moreinfo quit Aurelien Jarno wrote: > On Thu, Jun 30, 2011 at 11:45:19PM -0500, Jonathan Nieder wrote: >> That is, the crazy wireless router in this wireless network provides a >> nonrecursive DNS server through DHCP and although resolv.conf also >> inclu

Processed: Re: Bug#632273: libc6: resolving: does not try different nameserver after "recursion not available"

Processing commands for cont...@bugs.debian.org: > tag 632273 - upstream Bug #632273 [libc6] libc6: resolving: does not try different nameserver after "recursion not available" Removed tag(s) upstream. > tag 632273 + unreproducible Bug #632273 [libc6] libc6: resolving: does not try different name

Bug#632273: libc6: resolving: does not try different nameserver after "recursion not available"

tag 632273 - upstream tag 632273 + unreproducible thanks On Thu, Jun 30, 2011 at 11:45:19PM -0500, Jonathan Nieder wrote: > Package: libc6 > Version: 2.13-8 > Tags: upstream > > Typical amd64 experimental system. No ipv6 in sight. Since the last > upgrade[*] (libc6 2.13-7 -> 2.13-8), programs l

Bug#632273: libc6: resolving: does not try different nameserver after "recursion not available"

Package: libc6 Version: 2.13-8 Tags: upstream Typical amd64 experimental system. No ipv6 in sight. Since the last upgrade[*] (libc6 2.13-7 -> 2.13-8), programs like wget that use getaddrinfo are failing resolution instead of resolving some hosts: | $ wget http://repo.or.cz/ | --2011-06-30 23:37

Bug#632252: libc6: assertion error in res_query.c

Package: libc6 Version: 2.13-8 Severity: important Today I upgraded both chromium (the web browser) and libc6. I've seen cases when I open a new tab and quickly type in a site name where the browser crashes and upon reopening it and restoring my tabs, it crashes again. Repeat several times until

Bug#631878: fixed in tzdata 2011h-2

Hi, I can confirm that the same happens with a multistrap installation. tzdata cannot be configured: $> fakeroot fakechroot chroot debian-sid-armel-2011-06-30 dpkg --configure tzdata Setting up tzdata (2011h-2) ... dpkg: error processing tzdata (--configure): subprocess installed post-installat

r4774 - glibc-package/trunk/debian/patches/hurd-i386

Author: sthibault Date: 2011-06-30 17:56:58 + (Thu, 30 Jun 2011) New Revision: 4774 Modified: glibc-package/trunk/debian/patches/hurd-i386/submitted-ldsodefs.h.diff Log: Update patches/hurd-i386/submitted-ldsodefs.h.diff according to binutils decision Modified: glibc-package/trunk/debian/

Bug#632176: libc6: Needs to conflict with lib64* packages on amd64

On 2011-06-30 18:36 +0200, Jonathan Nieder wrote: > Sven Joachim wrote: > >> On multiarch-enabled i386 systems, installing libc6:amd64 together with >> lib64foo:i386 has some interesting effects. > [...] >> # apt-get install libc6:amd64 >> # apt-get install lib64ncurses5 >> # bash >> >> You get a

Bug#632176: libc6: Needs to conflict with lib64* packages on amd64

Hi Sven, Sven Joachim wrote: > On multiarch-enabled i386 systems, installing libc6:amd64 together with > lib64foo:i386 has some interesting effects. [...] > # apt-get install libc6:amd64 > # apt-get install lib64ncurses5 > # bash > > You get an error message: "bash: error while loading shared li

Processed: forcibly merging 632190 632196

Processing commands for cont...@bugs.debian.org: > forcemerge 632190 632196 Bug#632190: fails to install in cdebootstrap and debootstrap Bug#632196: libc6: unable to deboostrap as preinst thinks extracted files are copy Forcibly Merged 632190 632196. > thanks Stopping processing here. Please co

Bug#632196: libc6: unable to deboostrap as preinst thinks extracted files are copy

Package: libc6 Version: 2.13-8 Severity: normal Hi, attempting to (c)deboostrap sid with with 2.13-8 fails with the following: O: Unpacking libc6 (from .../libc6_2.13-8_amd64.deb) ... P: Unpacking package libc6 O: O: A copy of the C library was found in an unexpected directory: O: '/lib/x86_6

Processed: Re: Bug#630180: binutils: Emits GNU/Linux objects on hurd-i386

Processing commands for cont...@bugs.debian.org: > reassign 630180 libc0.3 Bug #630180 [binutils] binutils: Emits GNU/Linux objects on hurd-i386 Bug reassigned from package 'binutils' to 'libc0.3'. Bug No longer marked as found in versions binutils/2.21.51.20110421-3. > thanks Stopping processing

Bug#632190: fails to install in cdebootstrap and debootstrap

Package: libc6 Version: 2.13-8 Severity: important Hi Since eglibc was upgraded to 2.13-8 (this worked fine with eglibc 2.13-7, ignoring the unrelated issue between tzdata and cdebootstrap) cdebootstrap and debootstrap fail installing libc6: # cdebootstrap --debug -v --arch=amd64 sid /mnt/ http

Bug#632176: libc6: Needs to conflict with lib64* packages on amd64

Package: libc6 Version: 2.13-7 Severity: important User: vor...@debian.org Usertags: multiarch On multiarch-enabled i386 systems, installing libc6:amd64 together with lib64foo:i386 has some interesting effects. To reproduce, set up an i386 chroot with a dpkg from the pu/multiarch/full branch of g

Bug#631907: marked as done (libc6-dev: should add breaks for gcc without multiarch support)

Your message dated Thu, 30 Jun 2011 07:48:17 + with message-id and subject line Bug#631907: fixed in eglibc 2.13-8 has caused the Debian Bug report #631907, regarding libc6-dev: should add breaks for gcc without multiarch support to be marked as done. This means that you claim that the proble

Bug#631867: marked as done (sigev_notify_kqueue, SIGEV_KEVENT and SIGEV_THREAD_ID in )

Your message dated Thu, 30 Jun 2011 07:48:17 + with message-id and subject line Bug#631867: fixed in eglibc 2.13-8 has caused the Debian Bug report #631867, regarding sigev_notify_kqueue, SIGEV_KEVENT and SIGEV_THREAD_ID in to be marked as done. This means that you claim that the problem ha

Bug#630608: marked as done ([bash] Everything Segfaults After lib6 -7 Upgrade)

Your message dated Thu, 30 Jun 2011 07:48:17 + with message-id and subject line Bug#630608: fixed in eglibc 2.13-8 has caused the Debian Bug report #630608, regarding [bash] Everything Segfaults After lib6 -7 Upgrade to be marked as done. This means that you claim that the problem has been de

Bug#630699: marked as done (CVE-2011-1089: /etc/mtab corruption)

Your message dated Thu, 30 Jun 2011 07:48:17 + with message-id and subject line Bug#630699: fixed in eglibc 2.13-8 has caused the Debian Bug report #630699, regarding CVE-2011-1089: /etc/mtab corruption to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#626370: marked as done (CVE-2011-1659: Integer overflow in posix/fnmatch.c)

Your message dated Thu, 30 Jun 2011 07:48:17 + with message-id and subject line Bug#626370: fixed in eglibc 2.13-8 has caused the Debian Bug report #626370, regarding CVE-2011-1659: Integer overflow in posix/fnmatch.c to be marked as done. This means that you claim that the problem has been d

Bug#535504: marked as done (libc6: resolving: does not try different nameserver anymore)

Your message dated Thu, 30 Jun 2011 07:48:17 + with message-id and subject line Bug#602291: fixed in eglibc 2.13-8 has caused the Debian Bug report #602291, regarding libc6: resolving: does not try different nameserver anymore to be marked as done. This means that you claim that the problem h

Bug#602291: marked as done (icedove: Icedove does NOT use a second nameserver if the first responds with a server failure)

Your message dated Thu, 30 Jun 2011 07:48:17 + with message-id and subject line Bug#602291: fixed in eglibc 2.13-8 has caused the Debian Bug report #602291, regarding icedove: Icedove does NOT use a second nameserver if the first responds with a server failure to be marked as done. This mean

Bug#602291: marked as done (icedove: Icedove does NOT use a second nameserver if the first responds with a server failure)

Your message dated Thu, 30 Jun 2011 07:48:17 + with message-id and subject line Bug#535504: fixed in eglibc 2.13-8 has caused the Debian Bug report #535504, regarding icedove: Icedove does NOT use a second nameserver if the first responds with a server failure to be marked as done. This mean

Bug#535504: marked as done (libc6: resolving: does not try different nameserver anymore)

Your message dated Thu, 30 Jun 2011 07:48:17 + with message-id and subject line Bug#535504: fixed in eglibc 2.13-8 has caused the Debian Bug report #535504, regarding libc6: resolving: does not try different nameserver anymore to be marked as done. This means that you claim that the problem h

r4772 - glibc-package/trunk/debian

Author: aurel32 Date: 2011-06-30 07:26:30 + (Thu, 30 Jun 2011) New Revision: 4772 Modified: glibc-package/trunk/debian/changelog Log: New changelog entry Modified: glibc-package/trunk/debian/changelog === --- glibc-package/tr

r4770 - glibc-package/trunk/debian

Author: aurel32 Date: 2011-06-30 07:21:39 + (Thu, 30 Jun 2011) New Revision: 4770 Modified: glibc-package/trunk/debian/changelog Log: Upload to unstable Modified: glibc-package/trunk/debian/changelog === --- glibc-package/tru