Bug#164638: marked as done (libc6-dev: SIOCSIFNAME needs to be added)

2003-07-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Jul 2003 05:17:42 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#164638: fixed in glibc 2.3.2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#164638: marked as done (libc6-dev: SIOCSIFNAME needs to be added)

2003-07-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Jul 2003 05:17:42 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#164638: fixed in glibc 2.3.2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#164638: marked as done (libc6-dev: SIOCSIFNAME needs to be added)

2002-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2002 00:20:00 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#164638: libc6-dev: SIOCSIFNAME needs to be added has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#164638: marked as done (libc6-dev: SIOCSIFNAME needs to be added)

2002-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2002 00:20:00 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#164638: libc6-dev: SIOCSIFNAME needs to be added has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the