Bug#609389: marked as done (libc-bin: getconf -a have many variables set not properly (i.e. LEVEL*CACHE*))

2011-12-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Dec 2011 19:55:32 + with message-id and subject line Bug#609389: fixed in eglibc 2.11.3-1 has caused the Debian Bug report #609389, regarding libc-bin: getconf -a have many variables set not properly (i.e. LEVEL*CACHE*) to be marked as done. This means that you cla

Bug#609389: marked as done (libc-bin: getconf -a have many variables set not properly (i.e. LEVEL*CACHE*))

2011-12-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Dec 2011 22:48:30 + with message-id and subject line Bug#609389: fixed in eglibc 2.13-22 has caused the Debian Bug report #609389, regarding libc-bin: getconf -a have many variables set not properly (i.e. LEVEL*CACHE*) to be marked as done. This means that you clai

Bug#609389: marked as done (libc-bin: getconf -a have many variables set not properly (i.e. LEVEL*CACHE*))

2011-05-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 May 2011 19:48:42 + with message-id and subject line Bug#609389: fixed in eglibc 2.13-1 has caused the Debian Bug report #609389, regarding libc-bin: getconf -a have many variables set not properly (i.e. LEVEL*CACHE*) to be marked as done. This means that you claim

Bug#609389: marked as done (libc-bin: getconf -a have many variables set not properly (i.e. LEVEL*CACHE*))

2011-03-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Mar 2011 00:34:06 + with message-id and subject line Bug#609389: fixed in eglibc 2.13-0exp5 has caused the Debian Bug report #609389, regarding libc-bin: getconf -a have many variables set not properly (i.e. LEVEL*CACHE*) to be marked as done. This means that you c